pxcloud/vhost-device
5
0
Fork 0
mirror of https://github.com/rust-vmm/vhost-device.git synced 2025-12-31 02:41:56 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
4b6451176d
vhost-device/staging
History
Dorinda Bassey a2d9b2e721 sound: Improve function definition 
instead of consume() fn name, use read_output() fn which
is more appropriate and in sync with the write_input() fn.

Signed-off-by: Dorinda Bassey <dbassey@redhat.com>
2023-10-30 16:34:06 +05:30
..
vhost-device-sound sound: Improve function definition 2023-10-30 16:34:06 +05:30
vhost-device-video video: add v4l2 mocks 2023-10-24 11:17:33 +02:00
.gitignore Add new workspace under staging/ subdirectory 2023-10-11 16:25:00 +05:30
Cargo.lock video: add v4l2-decoder backend 2023-10-24 11:17:33 +02:00
Cargo.toml video: initial skeleton 2023-10-24 11:17:33 +02:00
coverage_config_x86_64.json staging: update coverage target 2023-10-24 19:09:41 +05:30
README.md Add new workspace under staging/ subdirectory 2023-10-11 16:25:00 +05:30

README.md

vhost-device staging workspace

This directory includes a separate Cargo workspace to include working vhost-user backend implementations that concern devices that have partial functionality and devices (and/or functionality) not yet ratified in the VIRTIO specification. For more details about vhost-device you can refer to the repository README.

To add a new member crate:

  1. Place it under this directory, ./staging.
  2. Append its name in the workspace.members array field of the workspace manifest file.
  3. Update the crate list in the repository README.

Testing and Continuous Integration

ℹ️ Notice ℹ️ : The CI runs on the root workspace only. This means that staging crates can have failing tests and bring down code coverage without automatic checks. Tests can still be run locally as part of the development process. To add a crate to the CI, add it to the root Cargo.toml workspace.members array as well as the staging manifest.