cloud-hypervisor/vm-virtio/Cargo.toml

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

[features]
default = []

[dependencies]
log = "0.4.14"
virtio-bindings = { version = "0.1", features = ["virtio-v5_0_0"]}
vm-memory = { version = "0.5.0", features = ["backend-mmap", "backend-atomic", "backend-bitmap"] }
vm-virtio: Initial crate Copied from Firecracker 17a9089d for the queue implementation and from crosvm 107edb3e for the device Trait. The device trait has some PCI specific methods hence its crosvm origin. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-04-18 19:24:06 +02:00			`[package]`
			`name = "vm-virtio"`
			`version = "0.1.0"`
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 13:25:19 +01:00			`authors = ["The Cloud Hypervisor Authors"]`
vm-virtio: Initial crate Copied from Firecracker 17a9089d for the queue implementation and from crosvm 107edb3e for the device Trait. The device trait has some PCI specific methods hence its crosvm origin. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-04-18 19:24:06 +02:00			`edition = "2018"`

build: make PCI (virtio and vfio) disableable at build time Although included by default it is now possible to build without PCI support. Signed-off-by: Rob Bradford <robert.bradford@intel.com> 2019-09-11 17:07:33 +01:00			`[features]`
			`default = []`

vm-virtio: Initial crate Copied from Firecracker 17a9089d for the queue implementation and from crosvm 107edb3e for the device Trait. The device trait has some PCI specific methods hence its crosvm origin. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-04-18 19:24:06 +02:00			`[dependencies]`
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"`
build: Use same virtio-bindings version Consistently use the crates.io 0.1.0 version based on Linux 5.0.0 Fixes: #1192 Signed-off-by: Rob Bradford <robert.bradford@intel.com> 2020-05-20 11:13:06 +01:00			`virtio-bindings = { version = "0.1", features = ["virtio-v5_0_0"]}`
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 12:08:04 -07:00			`vm-memory = { version = "0.5.0", features = ["backend-mmap", "backend-atomic", "backend-bitmap"] }`