pxcloud/vhost-device
5
0
Fork 0
mirror of https://github.com/rust-vmm/vhost-device.git synced 2025-12-26 22:48:17 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
937d28daee
vhost-device/staging
History
Manos Pitsidianakis 0a5249b903 gpu: guard gfxstream dependency with a feature 
Add a new compile-time feature, `gfxstream`, which is included in the
default features. The only thing that changes is that we can now build
without requiring the `gfxstream_backend` library on compilation time,
which helps in cases it is not packaged in a distro, or is not available
at a user's build machine.

Also update `README.md` with information about the build-time feature.

This commit does not change anything other than make gfxstream gpu mode
opt-out at build-time. Everything should continue to work the same.

Signed-off-by: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
2024-12-02 10:57:44 +01:00
..
vhost-device-gpu gpu: guard gfxstream dependency with a feature 2024-12-02 10:57:44 +01:00
vhost-device-video build(deps): bump the non-rust-vmm group across 2 directories with 13 updates 2024-12-02 10:43:14 +02:00
.gitignore Add new workspace under staging/ subdirectory 2023-10-11 16:25:00 +05:30
Cargo.lock build(deps): bump the non-rust-vmm group across 2 directories with 13 updates 2024-12-02 10:43:14 +02:00
Cargo.toml vhost-device-gpu: Add Initial Implementation 2024-11-20 15:02:02 +01:00
coverage_config_x86_64.json vhost-device-gpu: Add more tests for the crate 2024-11-29 15:37:03 +00:00
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.