pxcloud/vhost-device
5
0
Fork 0
mirror of https://github.com/rust-vmm/vhost-device.git synced 2025-12-27 15:45:44 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
a045950d74
vhost-device/staging
History
Matias Ezequiel Vara Larsen a045950d74 sound: remove ControlMessage from set_param() 
This commit removes ControlMessage in the set_param() method and
replaces it with the VirtioSndPcmSetParams structure that is already
parsed by the device. Both backends are able to handle that request
immediately so there is not need to pass ControlMessage to notify the
guest afterwards. By doing this, this commit removes any descriptor
manipulation from the audio backends. The commit fixes the test in pw.

Signed-off-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
2023-12-08 10:57:00 +05:30
..
vhost-device-sound sound: remove ControlMessage from set_param() 2023-12-08 10:57:00 +05:30
vhost-device-video vhost-device: Don't return bool unnecessarily 2023-12-01 09:40:52 +01:00
.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 4 updates 2023-12-04 10:52:14 +05:30
Cargo.toml video: initial skeleton 2023-10-24 11:17:33 +02:00
coverage_config_x86_64.json sound/test: add tests for virtio_sound.rs 2023-11-09 09:50:39 +02: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.