External/cloud-hypervisor
1
0
Fork 0
mirror of https://github.com/cloud-hypervisor/cloud-hypervisor.git synced 2024-12-25 23:25:19 +00:00
Code Issues Packages Projects Releases Wiki Activity
1446873b28
cloud-hypervisor/vm-device/Cargo.toml

21 lines
533 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.65 to 1.0.66 Bumps [anyhow](https://github.com/dtolnay/anyhow) from 1.0.65 to 1.0.66. - [Release notes](https://github.com/dtolnay/anyhow/releases) - [Commits](https://github.com/dtolnay/anyhow/compare/1.0.65...1.0.66) --- updated-dependencies: - dependency-name: anyhow dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-10-20 23:31:23 +00:00
anyhow = "1.0.66"
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.36 to 1.0.37 Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.36 to 1.0.37. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](https://github.com/dtolnay/thiserror/compare/1.0.36...1.0.37) --- updated-dependencies: - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-09-27 23:08:55 +00:00
thiserror = "1.0.37"
build: Update dependencies in v28.x stable branch Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-12-13 13:25:00 +00:00
serde = { version = "1.0.150", 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: Update dependencies in v28.x stable branch Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-12-13 13:25:00 +00:00
vm-memory = { version = "0.10.0", features = ["backend-mmap"] }
vmm-sys-util = "0.11.0"
vsock: vhost_user: vfio: Fix potential host memory overflow The vsock packets that we're building are resolving guest addresses to host ones and use the latter as raw pointers. If the corresponding guest mapped buffer spans across several regions in the guest, they will do so in the host as well. Since we have no guarantees that host regions are contiguous, it may lead the VMM into trying to access memory outside of its memory space. For now we fix that by ensuring that the guest buffers do not span across several regions. If they do, we error out. Ideally, we should enhance the rust-vmm memory model to support safe acces across host regions. Fixes CVE-2019-18960 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-12-12 13:08:34 +00:00
Reference in New Issue Copy Permalink