pxcloud/vhost-device
5
0
Fork 0
mirror of https://github.com/rust-vmm/vhost-device.git synced 2025-12-26 06:32:44 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
c7397703d4
vhost-device/staging
History
Timos Ampelikiotis c7397703d4 vhost-device-console: use worker's epoll for input events 
Eliminate the use of select and 'nix' package. This is done by
registering the input events (stdin or tcplistener) onto the main
worker's epoll.

Signed-off-by: Timos Ampelikiotis <t.ampelikiotis@virtualopensystems.com>
2024-11-09 16:41:28 +00:00
..
vhost-device-can build(deps): bump the vhost-device group across 1 directory with 37 updates 2024-11-04 17:43:55 +01:00
vhost-device-console vhost-device-console: use worker's epoll for input events 2024-11-09 16:41:28 +00:00
vhost-device-video build(deps): bump the vhost-device group across 1 directory with 37 updates 2024-11-04 17:43:55 +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 across 1 directory with 37 updates 2024-11-04 17:43:55 +01:00
Cargo.toml vhost-device-console: Add initial implementation 2024-08-29 17:11:30 +02:00
coverage_config_x86_64.json build(deps): bump rust-vmm-ci from 2122417 to 1150c47 2024-10-28 09:24:15 +01: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.