External/cloud-hypervisor
1
0
Fork 0
mirror of https://github.com/cloud-hypervisor/cloud-hypervisor.git synced 2024-11-05 11:31:14 +00:00
Code Issues Packages Projects Releases Wiki Activity
c1b962048c
cloud-hypervisor/virtio-devices/Cargo.toml

40 lines
1.2 KiB
TOML
Raw Normal View History

vm-virtio, virtio-devices: Split device implementation from virt queues Split the generic virtio code (queues and device type) from the VirtioDevice trait, transport and device implementations. This also simplifies the feature handling in vhost_user_backend as the vm-virtio crate is no longer has any features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-02 12:25:19 +00:00
[package]
name = "virtio-devices"
version = "0.1.0"
authors = ["The Cloud Hypervisor Authors"]
edition = "2018"
[features]
default = []
io_uring: Add new feature gate By adding a new io_uring feature gate, we let the user the possibility to choose if he wants to enable the io_uring improvements or not. Since the io_uring feature depends on the availability on recent host kernels, it's better if we leave it off for now. As soon as our CI will have support for a kernel 5.6 with all the features needed from io_uring, we'll enable this feature gate permanently. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-08-03 06:32:28 +00:00
io_uring = ["block_util/io_uring"]
vmm, virtio-devices: Extend mshv feature There are some seccomp rules needed for MSHV in virtio-devices but not for KVM. We only want to add those rules based on MSHV feature guard. Signed-off-by: Muminul Islam <muislam@microsoft.com>
2021-07-12 21:40:50 +00:00
mshv = []
vm-virtio, virtio-devices: Split device implementation from virt queues Split the generic virtio code (queues and device type) from the VirtioDevice trait, transport and device implementations. This also simplifies the feature handling in vhost_user_backend as the vm-virtio crate is no longer has any features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-02 12:25:19 +00:00
[dependencies]
anyhow = "1.0"
build: Update arc-swap dependency to 1.0.0 Also bump the vm-memory version to one that depends on arc-swap 1.0.0 too. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-11-16 11:56:15 +00:00
arc-swap = ">=1.0.0"
virtio-devices: seccomp: Add seccomp_filter module This patch added the seccomp_filter module to the virtio-devices crate by taking reference code from the vmm crate. This patch also adds allowed-list for the virtio-block worker thread. Partially fixes: #925 Signed-off-by: Bo Chen <chen.bo@intel.com>
2020-08-04 02:45:53 +00:00
block_util = { path = "../block_util" }
build(deps): bump byteorder from 1.4.2 to 1.4.3 Bumps [byteorder](https://github.com/BurntSushi/byteorder) from 1.4.2 to 1.4.3. - [Release notes](https://github.com/BurntSushi/byteorder/releases) - [Changelog](https://github.com/BurntSushi/byteorder/blob/master/CHANGELOG.md) - [Commits](https://github.com/BurntSushi/byteorder/compare/1.4.2...1.4.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-03-10 12:36:39 +00:00
byteorder = "1.4.3"
vm-virtio, virtio-devices: Split device implementation from virt queues Split the generic virtio code (queues and device type) from the VirtioDevice trait, transport and device implementations. This also simplifies the feature handling in vhost_user_backend as the vm-virtio crate is no longer has any features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-02 12:25:19 +00:00
epoll = ">=4.0.1"
virtio-devices: Report events for virtio device activation and reset Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-02-18 15:10:51 +00:00
event_monitor = { path = "../event_monitor" }
io-uring: Move to the crates.io 0.4.0 version Now that io-uring crate has been stabilized, let's move to the latest release 0.4.0 from crates.io. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-08-10 06:51:34 +00:00
io-uring = ">=0.4.0"
build: bump libc from 0.2.97 to 0.2.98 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.97 to 0.2.98. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.97...0.2.98) --- updated-dependencies: - dependency-name: libc dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-07-07 23:10:57 +00:00
libc = "0.2.98"
build(deps): bump log from 0.4.13 to 0.4.14 Bumps [log](https://github.com/rust-lang/log) from 0.4.13 to 0.4.14. - [Release notes](https://github.com/rust-lang/log/releases) - [Changelog](https://github.com/rust-lang/log/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/log/compare/0.4.13...0.4.14) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-01-27 03:17:53 +00:00
log = "0.4.14"
vm-virtio, virtio-devices: Split device implementation from virt queues Split the generic virtio code (queues and device type) from the VirtioDevice trait, transport and device implementations. This also simplifies the feature handling in vhost_user_backend as the vm-virtio crate is no longer has any features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-02 12:25:19 +00:00
net_gen = { path = "../net_gen" }
net_util = { path = "../net_util" }
virtio-devices: Remove mmio and pci differentiation Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-10-15 15:54:56 +00:00
pci = { path = "../pci" }
virtio-devices: Move the 'rate_limiter' module to its own crate To support I/O throttling on virt-net devices, we need to use the 'rate_limiter' module from the 'net_utils' crate. Given the 'virtio-devices' crate has dependency on the 'net_utils', we will need to move the 'rate_limiter' module out of the 'virtio-devices' crate to avoid circular dependency issue. Considering the 'rate_limiter' is not virtio specific and could be reused for non virtio devices, we move it to its own crate. Signed-off-by: Bo Chen <chen.bo@intel.com>
2021-03-22 18:23:51 +00:00
rate_limiter = { path = "../rate_limiter" }
build: bump seccomp from v0.24.4 to v0.24.5 Bumps [seccomp](https://github.com/firecracker-microvm/firecracker) from v0.24.4 to v0.24.5. - [Release notes](https://github.com/firecracker-microvm/firecracker/releases) - [Changelog](https://github.com/firecracker-microvm/firecracker/blob/cd36c699f3cb3d531289aadee26c45c1306edcfc/CHANGELOG.md) - [Commits](https://github.com/firecracker-microvm/firecracker/compare/8f44986a0e956a77f2b2324c12f73bec16130c82...cd36c699f3cb3d531289aadee26c45c1306edcfc) --- updated-dependencies: - dependency-name: seccomp dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2021-07-23 23:09:44 +00:00
seccomp = { git = "https://github.com/firecracker-microvm/firecracker", tag = "v0.24.5" }
vm-virtio, virtio-devices: Split device implementation from virt queues Split the generic virtio code (queues and device type) from the VirtioDevice trait, transport and device implementations. This also simplifies the feature handling in vhost_user_backend as the vm-virtio crate is no longer has any features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-02 12:25:19 +00:00
serde = ">=1.0.27"
serde_derive = ">=1.0.27"
serde_json = ">=1.0.9"
virtio-devices: Version state structures Version the state for device state for the virtio devices. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-06 13:34:31 +00:00
versionize = "0.1.6"
versionize_derive = "0.1.4"
vhost: Move to upstream crate The vhost crate from rust-vmm is ready, which is why we do the switch from the Cloud Hypervisor fork to the upstream crate. At the same time, we rename the crate from vhost_rs to vhost. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-02-25 09:46:27 +00:00
vhost = { git = "https://github.com/rust-vmm/vhost", branch = "master", package = "vhost", features = ["vhost-user-master", "vhost-user-slave"] }
vm-virtio, virtio-devices: Split device implementation from virt queues Split the generic virtio code (queues and device type) from the VirtioDevice trait, transport and device implementations. This also simplifies the feature handling in vhost_user_backend as the vm-virtio crate is no longer has any features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-02 12:25:19 +00:00
virtio-bindings = { version = "0.1", features = ["virtio-v5_0_0"]}
vm-allocator = { path = "../vm-allocator" }
vm-device = { path = "../vm-device" }
misc: Upgrade to use the vm-memory crate w/ dirty-page-tracking As the first step to complete live-migration with tracking dirty-pages written by the VMM, this commit patches the dependent vm-memory crate to the upstream version with the dirty-page-tracking capability. Most changes are due to the updated `GuestMemoryMmap`, `GuestRegionMmap`, and `MmapRegion` structs which are taking an additional generic type parameter to specify what 'bitmap backend' is used. The above changes should be transparent to the rest of the code base, e.g. all unit/integration tests should pass without additional changes. Signed-off-by: Bo Chen <chen.bo@intel.com>
2021-06-02 19:08:04 +00:00
vm-memory = { version = "0.5.0", features = ["backend-mmap", "backend-atomic", "backend-bitmap"] }
vm-virtio, virtio-devices: Split device implementation from virt queues Split the generic virtio code (queues and device type) from the VirtioDevice trait, transport and device implementations. This also simplifies the feature handling in vhost_user_backend as the vm-virtio crate is no longer has any features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-02 12:25:19 +00:00
vm-migration = { path = "../vm-migration" }
vm-virtio = { path = "../vm-virtio" }
vmm-sys-util = ">=0.3.1"
Reference in New Issue Copy Permalink