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.0", features = ["virtio-v5_0_0"] }
virtio-queue = { path = "../virtio-queue" }
vm-memory = { version = "0.6.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 17:24:06 +00: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 12:25:19 +00: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 17:24:06 +00: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 16:07:33 +00: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 17:24:06 +00: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 fixed versions in Cargo.toml files This doesn't really affect the build as we ship a Cargo.lock with fixed versions in. However for clarity it makes sense to use fixed versions throughout and let dependabot update them. Signed-off-by: Rob Bradford <robert.bradford@intel.com> 2021-08-06 09:11:40 +00:00			`virtio-bindings = { version = "0.1.0", features = ["virtio-v5_0_0"] }`
Move Cloud Hypervisor to virtio-queue crate Relying on the vm-virtio/virtio-queue crate from rust-vmm which has been copied inside the Cloud Hypervisor tree, the entire codebase is moved to the new definition of a Queue and other related structures. The reason for this move is to follow the upstream until we get some agreement for the patches that we need on top of that to make it properly work with Cloud Hypervisor. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> 2021-10-21 10:41:16 +00:00			`virtio-queue = { path = "../virtio-queue" }`
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> 2021-10-22 08:29:33 +00:00			`vm-memory = { version = "0.6.0", features = ["backend-mmap", "backend-atomic", "backend-bitmap"] }`