vhost-device/staging
Matias Ezequiel Vara Larsen a48138f8cd sound: skip musl builds
Disable builds for musl, where alsa-sys and pipewire build fail on
rust-vmm-container due to missing tools and headers. Alsa and Pipewire
backends are available only on gnu.

Signed-off-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
2024-01-02 15:54:13 +01:00
..
vhost-device-sound sound: skip musl builds 2024-01-02 15:54:13 +01:00
vhost-device-video build(deps): bump the vhost-device group in /staging with 16 updates 2024-01-02 12:00:19 +05:30
.gitignore Add new workspace under staging/ subdirectory 2023-10-11 16:25:00 +05:30
Cargo.lock build(deps): bump the vhost-device group in /staging with 16 updates 2024-01-02 12:00:19 +05:30
Cargo.toml video: initial skeleton 2023-10-24 11:17:33 +02:00
coverage_config_x86_64.json staging: update coverage score 2023-12-14 21:41:14 +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.