crosvm/third_party/vmm_vhost
David Stevens 60aa43629a devices: vhost-user: add protocol flag for shmem
Add a vhost protocol feature flag for shared memory region support. This
is necessary to avoid sending the GET_SHARED_MEMORY_REGIONS message to
backends which don't support it.

BUG=b:252901073
TEST=crosvm device wl

Change-Id: I044926e982526c3c76063b5386cab0db72524707
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3951472
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Commit-Queue: David Stevens <stevensd@chromium.org>
2022-10-21 01:09:07 +00:00
..
.buildkite
.cargo
.github
docs
src devices: vhost-user: add protocol flag for shmem 2022-10-21 01:09:07 +00:00
.gitignore
.gitmodules
Cargo.toml devices: Implement MasterReqHandler for Windows 2022-09-12 16:09:34 +00:00
CODEOWNERS
LICENSE
LICENSE-BSD-3-Clause
LICENSE-BSD-Chromium
README.md vmm_vhost: Enable health-check for third_party/vmm_vhost 2022-09-01 15:05:31 +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.