mirror of
https://github.com/rust-vmm/vhost-device.git
synced 2026-01-11 16:36:15 +00:00
Merge branch 'main' into i2c/unused-mem
This commit is contained in:
commit
aa6a2450d5
@ -1,2 +1,2 @@
|
||||
# Add the list of code owners here (using their GitHub username)
|
||||
* gatekeeper-PullAssigner @vireshk
|
||||
* gatekeeper-PullAssigner @vireshk @stsquad @mathieupoirier
|
||||
|
||||
17
README.md
17
README.md
@ -9,3 +9,20 @@ crates.
|
||||
Here is the list of device backends that we support:
|
||||
|
||||
- [I2C](https://github.com/rust-vmm/vhost-device/blob/master/src/i2c/README.md)
|
||||
|
||||
## Separation of Concerns
|
||||
|
||||
The binaries built by this repository can be run with any VMM which
|
||||
can act as a vhost-user master. Typically they have been tested with
|
||||
[QEMU](https://www.qemu.org) although the rust-vmm project does
|
||||
provide a [vhost-user
|
||||
master](https://github.com/rust-vmm/vhost/tree/main/src/vhost_user)
|
||||
crate for rust based VMMs.
|
||||
|
||||
While it's possible to implement all parts of the backend inside the
|
||||
vhost-device workspace consideration should be given to separating the
|
||||
VirtQueue handling and response logic to a crate in [vm-virtio
|
||||
devices](https://github.com/rust-vmm/vm-virtio/tree/main/crates/devices).
|
||||
This way a monolithic rust-vmm VMM implementation can reuse the core
|
||||
logic to service the virtio requests directly in the application.
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user