While there may be some work to do on the testing framework to make proper use of vm-virtio we should at least document the desire for modularity. Signed-off-by: Alex Bennée <alex.bennee@linaro.org> |
||
|---|---|---|
| .cargo | ||
| .github | ||
| rust-vmm-ci@b037be3396 | ||
| src/i2c | ||
| .gitignore | ||
| .gitmodules | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CODEOWNERS | ||
| coverage_config_x86_64.json | ||
| LICENSE-APACHE | ||
| README.md | ||
vhost-device
Design
This repository hosts various 'vhost-user' device backends in their own crates. See their individual README.md files for specific information about those crates.
Here is the list of device backends that we support:
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 although the rust-vmm project does provide a vhost-user master 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. This way a monolithic rust-vmm VMM implementation can reuse the core logic to service the virtio requests directly in the application.