External/cloud-hypervisor
1
0
Fork 0
mirror of https://github.com/cloud-hypervisor/cloud-hypervisor.git synced 2024-11-05 03:21:13 +00:00
Code Issues Packages Projects Releases Wiki Activity
28d4957ba5
cloud-hypervisor/vm-device/Cargo.toml

20 lines
532 B
TOML
Raw Normal View History

vm-device: Add new crate for virtio and VFIO agnostic traits The new crate vm-device is created here to host the definitions of traits not meant to be tied to virtio of VFIO specifically. We need to add a new trait to update external DMA mappings for devices, which is why the vm-device crate is the right fit for this. We can expect this crate to be extended later once the design gets approved from a rust-vmm perspective. In this specific use case, we can have some devices like VFIO or vhost-user ones requiring to be notified about mapping updates. This new trait ExternalDmaMapping will allow such devices to implement their own way to handle such event. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-07 16:57:19 +00:00
[package]
name = "vm-device"
version = "0.1.0"
authors = ["The Cloud Hypervisor Authors"]
build: migrate to Rust 2021 edition Rust 2021 edition has a few improvements over the 2018 edition. Migrate the project to 2021 edition by following recommended migration steps. Luckily, the code itself doesn't require fixing. Bump MSRV to 1.56 as it is required by the 2021 edition. Also fix the clap build dependency to make Cloud Hypervisor build again. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-04-08 15:11:04 +00:00
edition = "2021"
vm-device: Add new crate for virtio and VFIO agnostic traits The new crate vm-device is created here to host the definitions of traits not meant to be tied to virtio of VFIO specifically. We need to add a new trait to update external DMA mappings for devices, which is why the vm-device crate is the right fit for this. We can expect this crate to be extended later once the design gets approved from a rust-vmm perspective. In this specific use case, we can have some devices like VFIO or vhost-user ones requiring to be notified about mapping updates. This new trait ExternalDmaMapping will allow such devices to implement their own way to handle such event. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-07 16:57:19 +00:00
vmm, vm-device: make use of the kvm feature gate in vfio-ioctls The vfio-ioctls crate now contains a KVM feature gate. Make use of it in Cloud Hypervisor. That crate has two users. For the vmm crate is it straight-forward. For the vm-device crate, we introduce a KVM feature gate as well so that the vmm crate can pass on the configuration. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2021-07-13 16:04:32 +00:00
[features]
default = []
kvm = ["vfio-ioctls/kvm"]
build: use vfio-ioctls that supports MSHV Disable default features and propagate hypervisor selection where necessary. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2021-09-02 09:44:08 +00:00
mshv = ["vfio-ioctls/mshv"]
vmm, vm-device: make use of the kvm feature gate in vfio-ioctls The vfio-ioctls crate now contains a KVM feature gate. Make use of it in Cloud Hypervisor. That crate has two users. For the vmm crate is it straight-forward. For the vm-device crate, we introduce a KVM feature gate as well so that the vmm crate can pass on the configuration. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2021-07-13 16:04:32 +00:00
vm-device: Add new crate for virtio and VFIO agnostic traits The new crate vm-device is created here to host the definitions of traits not meant to be tied to virtio of VFIO specifically. We need to add a new trait to update external DMA mappings for devices, which is why the vm-device crate is the right fit for this. We can expect this crate to be extended later once the design gets approved from a rust-vmm perspective. In this specific use case, we can have some devices like VFIO or vhost-user ones requiring to be notified about mapping updates. This new trait ExternalDmaMapping will allow such devices to implement their own way to handle such event. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-07 16:57:19 +00:00
[dependencies]
build: Bump anyhow from 1.0.75 to 1.0.79 Bumps [anyhow](https://github.com/dtolnay/anyhow) from 1.0.75 to 1.0.79. - [Release notes](https://github.com/dtolnay/anyhow/releases) - [Commits](https://github.com/dtolnay/anyhow/compare/1.0.75...1.0.79) --- updated-dependencies: - dependency-name: anyhow dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-01-08 22:39:02 +00:00
anyhow = "1.0.79"
hypervisor, vm-device: Relocate InterruptSourceConfig Move this enum from vm-device to hypervisor crate so that hypervisor crate does not gain an extra dependency. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-05-10 21:23:18 +00:00
hypervisor = { path = "../hypervisor" }
build: Bump thiserror from 1.0.40 to 1.0.52 Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.40 to 1.0.52. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](https://github.com/dtolnay/thiserror/compare/1.0.40...1.0.52) --- updated-dependencies: - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-29 23:11:34 +00:00
thiserror = "1.0.52"
build: Bump serde from 1.0.193 to 1.0.196 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.193 to 1.0.196. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.193...v1.0.196) --- updated-dependencies: - dependency-name: serde dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-09 23:04:35 +00:00
serde = { version = "1.0.196", features = ["rc", "derive"] }
vfio-ioctls: Move away from archived crate rust-vmm/vfio-ioctls Make sure Cloud Hypervisor relies on upstream and actively maintained vfio-ioctls crate from the rust-vmm/vfio repository instead of the deprecated version coming from rust-vmm/vfio-ioctls repository. Fixes #3673 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2022-02-04 10:58:01 +00:00
vfio-ioctls = { git = "https://github.com/rust-vmm/vfio", branch = "main", default-features = false }
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
vm-memory = { version = "0.14.0", features = ["backend-mmap"] }
vmm-sys-util = "0.12.1"
Reference in New Issue Copy Permalink