vhost-device/staging
dependabot[bot] bad9efe4eb build(deps): bump humantime from 2.1.0 to 2.2.0 in /staging
Bumps [humantime](https://github.com/chronotope/humantime) from 2.1.0 to 2.2.0.
- [Commits](https://github.com/chronotope/humantime/commits)

---
updated-dependencies:
- dependency-name: humantime
  dependency-version: 2.2.0
  dependency-type: indirect
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2025-04-01 10:40:42 +02:00
..
vhost-device-video build(deps): bump the non-rust-vmm group across 2 directories with 19 updates 2025-03-04 10:01:56 +01:00
.gitignore Add new workspace under staging/ subdirectory 2023-10-11 16:25:00 +05:30
Cargo.lock build(deps): bump humantime from 2.1.0 to 2.2.0 in /staging 2025-04-01 10:40:42 +02:00
Cargo.toml Move vhost-user-gpu from staging to main directory 2025-02-14 10:15:52 +02:00
coverage_config_x86_64.json Move vhost-user-gpu from staging to main directory 2025-02-14 10:15:52 +02:00
README.md Add new workspace under staging/ subdirectory 2023-10-11 16:25:00 +05:30

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.