2020-07-02 12:25:19 +00:00
|
|
|
[package]
|
|
|
|
|
name = "virtio-devices"
|
|
|
|
|
version = "0.1.0"
|
|
|
|
|
authors = ["The Cloud Hypervisor Authors"]
|
2022-04-08 15:11:04 +00:00
|
|
|
edition = "2021"
|
2020-07-02 12:25:19 +00:00
|
|
|
|
|
|
|
|
[features]
|
|
|
|
|
default = []
|
|
|
|
|
|
|
|
|
|
[dependencies]
|
2024-01-08 22:39:02 +00:00
|
|
|
anyhow = "1.0.79"
|
2022-08-02 07:14:59 +00:00
|
|
|
arc-swap = "1.5.1"
|
2023-07-12 02:24:28 +00:00
|
|
|
block = { path = "../block" }
|
2024-03-29 23:33:33 +00:00
|
|
|
byteorder = "1.5.0"
|
2023-07-04 23:04:49 +00:00
|
|
|
epoll = "4.3.3"
|
2021-02-18 15:10:51 +00:00
|
|
|
event_monitor = { path = "../event_monitor" }
|
2024-02-07 23:15:53 +00:00
|
|
|
libc = "0.2.153"
|
2023-11-23 23:47:38 +00:00
|
|
|
log = "0.4.20"
|
2020-07-02 12:25:19 +00:00
|
|
|
net_gen = { path = "../net_gen" }
|
|
|
|
|
net_util = { path = "../net_util" }
|
2020-10-15 15:54:56 +00:00
|
|
|
pci = { path = "../pci" }
|
2021-03-22 18:23:51 +00:00
|
|
|
rate_limiter = { path = "../rate_limiter" }
|
2023-10-30 18:31:10 +00:00
|
|
|
seccompiler = "0.4.0"
|
2024-02-09 23:04:35 +00:00
|
|
|
serde = { version = "1.0.196", features = ["derive"] }
|
2024-03-01 23:49:27 +00:00
|
|
|
serde_json = "1.0.114"
|
2022-08-25 08:38:42 +00:00
|
|
|
serial_buffer = { path = "../serial_buffer" }
|
2023-12-29 23:11:34 +00:00
|
|
|
thiserror = "1.0.52"
|
build: Bump vmm-sys-util crate and its consumers
This patch bumps the following crates, including `kvm-bindings@0.7.0`*,
`kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`,
`versionize_derive@0.1.6`***, `vhost@0.10.0`,
`vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`,
`vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`,
`mshv-bindings`,`mshv-ioctls`, and `vfio-user`.
* A fork of the `kvm-bindings` crate is being used to support
serialization of various structs for migration [1]. Also, code changes
are made to accommodate the updated `struct xsave` from the Linux
kernel. Note: these changes related to `struct xsave` break
live-upgrade.
** The new `kvm-ioctls` crate introduced breaking changes for
the `get/set_one_reg` API on `aarch64` [2], so code changes are made to
the new APIs.
*** A fork of the `versionize_derive` crate is being used to support
versionize on packed structs [3].
[1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0
[2] https://github.com/rust-vmm/kvm-ioctls/pull/223
[3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6
Fixes: #6072
Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
|
|
|
versionize = "0.2.0"
|
|
|
|
|
versionize_derive = "0.1.6"
|
|
|
|
|
vhost = { version = "0.10.0", features = ["vhost-user-frontend", "vhost-user-backend", "vhost-kern", "vhost-vdpa"] }
|
2023-02-21 23:58:46 +00:00
|
|
|
virtio-bindings = { version = "0.2.0", features = ["virtio-v5_0_0"] }
|
build: Bump vmm-sys-util crate and its consumers
This patch bumps the following crates, including `kvm-bindings@0.7.0`*,
`kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`,
`versionize_derive@0.1.6`***, `vhost@0.10.0`,
`vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`,
`vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`,
`mshv-bindings`,`mshv-ioctls`, and `vfio-user`.
* A fork of the `kvm-bindings` crate is being used to support
serialization of various structs for migration [1]. Also, code changes
are made to accommodate the updated `struct xsave` from the Linux
kernel. Note: these changes related to `struct xsave` break
live-upgrade.
** The new `kvm-ioctls` crate introduced breaking changes for
the `get/set_one_reg` API on `aarch64` [2], so code changes are made to
the new APIs.
*** A fork of the `versionize_derive` crate is being used to support
versionize on packed structs [3].
[1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0
[2] https://github.com/rust-vmm/kvm-ioctls/pull/223
[3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6
Fixes: #6072
Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
|
|
|
virtio-queue = "0.11.0"
|
2020-07-02 12:25:19 +00:00
|
|
|
vm-allocator = { path = "../vm-allocator" }
|
|
|
|
|
vm-device = { path = "../vm-device" }
|
2024-04-02 23:22:11 +00:00
|
|
|
vm-memory = { version = "0.14.1", features = ["backend-mmap", "backend-atomic", "backend-bitmap"] }
|
2020-07-02 12:25:19 +00:00
|
|
|
vm-migration = { path = "../vm-migration" }
|
|
|
|
|
vm-virtio = { path = "../vm-virtio" }
|
build: Bump vmm-sys-util crate and its consumers
This patch bumps the following crates, including `kvm-bindings@0.7.0`*,
`kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`,
`versionize_derive@0.1.6`***, `vhost@0.10.0`,
`vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`,
`vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`,
`mshv-bindings`,`mshv-ioctls`, and `vfio-user`.
* A fork of the `kvm-bindings` crate is being used to support
serialization of various structs for migration [1]. Also, code changes
are made to accommodate the updated `struct xsave` from the Linux
kernel. Note: these changes related to `struct xsave` break
live-upgrade.
** The new `kvm-ioctls` crate introduced breaking changes for
the `get/set_one_reg` API on `aarch64` [2], so code changes are made to
the new APIs.
*** A fork of the `versionize_derive` crate is being used to support
versionize on packed structs [3].
[1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0
[2] https://github.com/rust-vmm/kvm-ioctls/pull/223
[3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6
Fixes: #6072
Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
|
|
|
vmm-sys-util = "0.12.1"
|
