commit | 98298cb96972c20e05bffed58861456b48328d43 | [log] [tgz] |
---|---|---|
author | Keiichi Watanabe <keiichiw@chromium.org> | Mon Mar 15 02:28:15 2021 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Mar 16 01:01:09 2021 |
tree | 86716cd42cd9a3fe1474884a234389fac79ee4e1 | |
parent | ab426ef7974bb72b6811a4a82cc1fae5c243d793 [diff] |
CHROMIUM: Ignore vsock test cases Disable vsock test cases accessing /dev/vhost-vsock, which is unavailable in chroot. BUG=b:181227406 TEST=cargo test --all-features in chroot Change-Id: I99a80330597c7e281f73ed60aa798ec99f307e3a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/rust-vmm/vhost/+/2759311 Tested-by: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Chirantan Ekbote <chirantan@chromium.org> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org>
A pure rust library for vDPA, vhost and vhost-user.
The vhost
crate aims to help implementing dataplane for virtio backend drivers. It supports three different types of dataplane drivers:
The main relationship among Traits and Structs exported by the vhost
crate is as below:
The vhost drivers in Linux provide in-kernel virtio device emulation. Normally the hypervisor userspace process emulates I/O accesses from the guest. Vhost puts virtio emulation code into the kernel, taking hypervisor userspace out of the picture. This allows device emulation code to directly call into kernel subsystems instead of performing system calls from userspace. The hypervisor relies on ioctl based interfaces to control those in-kernel vhost drivers, such as vhost-net, vhost-scsi and vhost-vsock etc.
The vhost-user protocol aims to implement vhost backend drivers in userspace, which complements the ioctl interface used to control the vhost implementation in the Linux kernel. It implements the control plane needed to establish virtqueue sharing with a user space process on the same host. It uses communication over a Unix domain socket to share file descriptors in the ancillary data of the message.
The protocol defines two sides of the communication, master and slave. Master is the application that shares its virtqueues, slave is the consumer of the virtqueues. Master and slave can be either a client (i.e. connecting) or server (listening) in the socket communication.