vhost-device/staging
Manos Pitsidianakis 3eaa0f80f1 gpu: Make some formatting changes to README.md
- Add missing `--gpu-mode` argument from "Synopsis" section"
- Make "Options" section shorter, include --gpu-mode and its possible
  values
- Surround source code identifiers with backticks so they render as code
- Split "Features" section in paragraphs in preparation for next commit,
  which will expand the "gfxstream" part with info about compilation
  details.
- Surround gpu mode values with backticks so they render as code

Signed-off-by: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
2024-12-02 10:57:44 +01:00
..
vhost-device-gpu gpu: Make some formatting changes to README.md 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

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.