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
b930b3fb41
cloud-hypervisor/vm-virtio/Cargo.toml

34 lines
836 B
TOML
Raw Normal View History

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"
authors = ["Samuel Ortiz <sameo@linux.intel.com>"]
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 = []
pci_support = ["pci"]
vm-virtio: Add MMIO transport Derived from the crosvm code at 5656c124af2bb956dba19e409a269ca588c685e3 and adapted to work within cloud-hypervisor: Main differences: * Interrupt handling is done via a VirtioInterrupt turned into a devices::Interrupt * GuestMemory -> GuestMemoryMmap * Differences in read/write for BusDevice * Different crates for EventFd and GuestAddress Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-09-11 16:20:12 +00:00
mmio_support = []
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
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: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
byteorder = "1.3.2"
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
devices = { path = "../devices" }
cargo: Update micro_http Update micro_http create to allow set content type. Suggested-by: Samuel Ortiz <sameo@linux.intel.com> Tested-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com> Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>
2019-11-08 17:49:51 +00:00
epoll = ">=4.0.1"
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
libc = "0.2.60"
log = "0.4.8"
vm-virtio: Create virtio-net device In order to provide connectivity through network interface between host and guest, this patch introduces the virtio-net backend. This code is based on Firecracker commit d4a89cdc0bd2867f821e3678328dabad6dd8b767 It is a trimmed down version of the original files as it removes the rate limiter support. It has been ported to support vm-memory crate and the epoll handler has been modified in order to run a dedicated epoll loop from the device itself. This epoll loop runs in its own dedicated thread. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-05-08 00:26:37 +00:00
net_gen = { path = "../net_gen" }
net_util = { path = "../net_util" }
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
pci = { path = "../pci", optional = true }
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
tempfile = "3.1.0"
virtio-bindings: Rely on the upstream crate from rust-vmm Now that virtio-bindings is a crate part of the rust-vmm project, we want to rely on this one instead of the local one we had so far. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-09-19 13:42:29 +00:00
virtio-bindings = { git = "https://github.com/rust-vmm/virtio-bindings", version = "0.1", features = ["virtio-v5_0_0"]}
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
vm-allocator = { path = "../vm-allocator" }
vm-virtio: Trigger external map/unmap from virtio-iommu This patch relies on the trait implementation provided for each device which requires some sort of external update based on a map or unmap. Whenever a MAP or UNMAP request comes through the virtqueues, it triggers a call to the external mapping trait with map()/unmap() functions being invoked. Those external mappings are meant to be used from VFIO and vhost-user devices as they need to update their own mappings. In case of VFIO, the goal is to update the DMAR table in the physical IOMMU, while vhost-user devices needs to update their internal representation of the virtqueues. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-08 00:12:11 +00:00
vm-device = { path = "../vm-device" }
cargo: Update to the latest kvm-ioctls version We need to rely on the latest kvm-ioctls version to benefit from the recent addition of unregister_ioevent(), allowing us to detach a previously registered eventfd to a PIO or MMIO guest address. Because of this update, we had to modify the current constraint we had on the vmm-sys-util crate, using ">= 0.1.1" instead of being strictly tied to "0.2.0". Once the dependency conflict resolved, this commit took care of fixing build issues caused by recent modification of kvm-ioctls relying on EventFd reference instead of RawFd. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-30 16:38:38 +00:00
vmm-sys-util = ">=0.1.1"
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
vm-virtio: Add vhost-user-fs support The vhost-user-fs or virtio-fs device allows files and directories to be shared between host and guest. This patch adds the implementation of this device to the cloud-hypervisor device model. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-05-21 18:54:53 +00:00
[dependencies.vhost_rs]
path = "../vhost_rs"
features = ["vhost-user-master"]
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.vm-memory]
git = "https://github.com/rust-vmm/vm-memory"
features = ["backend-mmap"]
Reference in New Issue Copy Permalink