crosvm/third_party/vmm_vhost
Keiichi Watanabe b757f0d398 vmm_vhost: vfio: Remove unused File return value
BUG=none
TEST=build

Change-Id: I3f031c9d6488c9380fd328182d8f0ef00bad0c68
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3474158
Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
Tested-by: kokoro <noreply+kokoro@google.com>
Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org>
2022-02-22 06:50:11 +00:00
..
.buildkite
.cargo
.github
docs vmm_vhost: Delete vhost-kern and vhost-vsock 2021-12-01 09:45:44 +00:00
src vmm_vhost: vfio: Remove unused File return value 2022-02-22 06:50:11 +00:00
.gitignore
.gitmodules
Cargo.toml Prepare vmm_vhost to be milti-platform 2/2 2022-02-15 20:56:20 +00:00
CODEOWNERS
LICENSE
LICENSE-BSD-3-Clause
LICENSE-BSD-Chromium
README.md vmm_vhost: Delete vhost-kern and vhost-vsock 2021-12-01 09:45:44 +00:00

vHost

A pure rust library for vhost-user. This is a fork of rust-vmm/vhost.

vhost Architecture

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.