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

34 lines
994 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]
vm-virtio: Add the ability to serialize a Queue This commit relies on serde to serialize and deserialize the content of a Queue structure. This will be useful information to store when implementing snapshot/restore feature for virtio devices. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: Yi Sun <yi.y.sun@linux.intel.com>
2020-04-08 01:53:12 +00:00
anyhow = "1.0"
vm-virtio, vmm, vfio: Store GuestMemoryMmap in an Arc<ArcSwap<T>> This allows us to change the memory map that is being used by the devices via an atomic swap (by replacing the map with another one). The ArcSwap provides the mechanism for atomically swapping from to another whilst still giving good read performace. It is inside an Arc so that we can use a single ArcSwap for all users. Not covered by this change is replacing the GuestMemoryMmap itself. This change also removes some vertical whitespace from use blocks in the files that this commit also changed. Vertical whitespace was being used inconsistently and broke rustfmt's behaviour of ordering the imports as it would only do it within the block. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-31 10:49:11 +00:00
arc-swap = ">=0.4.4"
build(deps): bump byteorder from 1.3.2 to 1.3.4 Bumps [byteorder](https://github.com/BurntSushi/byteorder) from 1.3.2 to 1.3.4. - [Release notes](https://github.com/BurntSushi/byteorder/releases) - [Changelog](https://github.com/BurntSushi/byteorder/blob/master/CHANGELOG.md) - [Commits](https://github.com/BurntSushi/byteorder/compare/1.3.2...1.3.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-02-07 13:44:37 +00:00
byteorder = "1.3.4"
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(deps): bump libc from 0.2.69 to 0.2.70 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.69 to 0.2.70. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.69...0.2.70) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-05-12 16:34:25 +00:00
libc = "0.2.70"
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
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 }
vm-virtio: Add the ability to serialize a Queue This commit relies on serde to serialize and deserialize the content of a Queue structure. This will be useful information to store when implementing snapshot/restore feature for virtio devices. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: Yi Sun <yi.y.sun@linux.intel.com>
2020-04-08 01:53:12 +00:00
serde = ">=1.0.27"
serde_derive = ">=1.0.27"
serde_json = ">=1.0.9"
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"
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 10:13:06 +00:00
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" }
build: Bump vm-memory and linux-loader dependencies linux-loader depends on vm-memory so must be updated at the same time. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-03-23 13:54:34 +00:00
vm-memory = { version = "0.2.0", features = ["backend-mmap", "backend-atomic"] }
vm-migration: Define the Snapshottable and Transportable traits A Snapshottable component can snapshot itself and provide a MigrationSnapshot payload as a result. A MigrationSnapshot payload is a map of component IDs to a list of migration sections (MigrationSection). As component can be made of several Migratable sub-components (e.g. the DeviceManager and its device objects), a migration snapshot can be made of multiple snapshot itself. A snapshot is a list of migration sections, each section being a component state snapshot. Having multiple sections allows for easier and backward compatible migration payload extensions. Once created, a migratable component snapshot may be transported and this is what the Transportable trait defines, through 2 methods: send and recv. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: Yi Sun <yi.y.sun@linux.intel.com>
2019-05-01 16:59:51 +00:00
vm-migration = { path = "../vm-migration" }
vmm: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
vmm-sys-util = ">=0.3.1"
Cargo: switch vhost_rs to external crate As cloud-hypervisor/vhost crate (dragonball branch) is ready to be used, switch vhost_rs from internal crate to the external one. Signed-off-by: Eryu Guan <eguan@linux.alibaba.com>
2020-02-25 03:26:35 +00:00
vhost_rs = { git = "https://github.com/cloud-hypervisor/vhost", branch = "dragonball", package = "vhost", features = ["vhost-user-master", "vhost-user-slave"] }
Reference in New Issue Copy Permalink