cloud-hypervisor/vm-device/Cargo.toml

[package]
name = "vm-device"
version = "0.1.0"
authors = ["The Cloud Hypervisor Authors"]
edition = "2018"

[dependencies]
anyhow = "1.0"
thiserror = "1.0"
serde = {version = ">=1.0.27", features = ["rc"] }
serde_derive = ">=1.0.27"
serde_json = ">=1.0.9"
vm-memory = { version = "0.5.0", features = ["backend-mmap"] }
vmm-sys-util = ">=0.3.1"
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 09:57:19 -07:00			`[package]`
			`name = "vm-device"`
			`version = "0.1.0"`
			`authors = ["The Cloud Hypervisor Authors"]`
			`edition = "2018"`

			`[dependencies]`
vm-device: Initial Migratable trait The Migratable trait groups all expected capabilities of devices and components that can be migrated. For a component to be migrated, it must be able to pause and resume. Once paused, it should be able to provide a snapshot of itself. It should also be able to restore itself from a snaphot. As a consequence, the Migratable trait will be split between the Pausable and the Snapshotable traits. This commit only adds the Pausable one. All migratable devices will be tracked from the DeviceManager. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-11-18 15:30:54 +01:00			`anyhow = "1.0"`
			`thiserror = "1.0"`
			`serde = {version = ">=1.0.27", features = ["rc"] }`
			`serde_derive = ">=1.0.27"`
			`serde_json = ">=1.0.9"`
build(deps): bump vm-memory from 0.4.0 to 0.5.0 Bumps [vm-memory](https://github.com/rust-vmm/vm-memory) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/rust-vmm/vm-memory/releases) - [Changelog](https://github.com/rust-vmm/vm-memory/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-vmm/vm-memory/compare/v0.4.0...v0.5.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> 2021-02-10 09:54:08 +00:00			`vm-memory = { version = "0.5.0", features = ["backend-mmap"] }`
vm-device: Introduce InterruptManager and InterruptSourceGroup traits These new traits are meant to abstract the knowledge about the hypervisor and the type of interrupt being used from the perspective of the devices. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> 2020-01-14 10:45:06 +01:00			`vmm-sys-util = ">=0.3.1"`
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 14:08:34 +01:00