cloud-hypervisor/devices/Cargo.toml

[package]
name = "devices"
version = "0.1.0"
authors = ["The Chromium OS Authors"]

[dependencies]
byteorder = ">=1.2.1"
epoll = "=4.0.1"
kvm-bindings = "0.1"
kvm-ioctls = { git = "https://github.com/rust-vmm/kvm-ioctls", branch = "master" }
libc = ">=0.2.39"
log = "*"
vm-memory = { git = "https://github.com/rust-vmm/vm-memory" }
vmm-sys-util = { git = "https://github.com/rust-vmm/vmm-sys-util" }

[dev-dependencies]
tempfile = ">=3.0.2"
cloud-hypervisor: Add devices crate Based on the Firecracker devices crate from commit 9cdb5b2. It is a trimmed down version compared to the Firecracker one, to remove a bunch of pulled dependencies (logger, metrics, rate limiter, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-03-07 13:56:43 +00:00			`[package]`
			`name = "devices"`
			`version = "0.1.0"`
			`authors = ["The Chromium OS Authors"]`

			`[dependencies]`
			`byteorder = ">=1.2.1"`
			`epoll = "=4.0.1"`
devices: Add userspace IOAPIC implementation The goal for cloud-hypervisor is to keep the host safe. With this in mind, we want to emulate as much as possible in userspace instead of in kernel directly. The IOAPIC is a good candidate to move from kernel to userspace, which is why this commit introduces a userspace implementation of the IOAPIC 82093AA based on the documentation: https://pdos.csail.mit.edu/6.828/2016/readings/ia32/ioapic.pdf This code is inspired from the files devices/src/ioapic.rs and devices/src/split_irqchip_common.rs from the crosvm codebase. The reference version used being 6c1e23eee3065b3f3d6fc4fb992ac9884dbabf68. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> 2019-06-12 08:12:45 +00:00			`kvm-bindings = "0.1"`
			`kvm-ioctls = { git = "https://github.com/rust-vmm/kvm-ioctls", branch = "master" }`
cloud-hypervisor: Add devices crate Based on the Firecracker devices crate from commit 9cdb5b2. It is a trimmed down version compared to the Firecracker one, to remove a bunch of pulled dependencies (logger, metrics, rate limiter, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-03-07 13:56:43 +00:00			`libc = ">=0.2.39"`
devices: Add userspace IOAPIC implementation The goal for cloud-hypervisor is to keep the host safe. With this in mind, we want to emulate as much as possible in userspace instead of in kernel directly. The IOAPIC is a good candidate to move from kernel to userspace, which is why this commit introduces a userspace implementation of the IOAPIC 82093AA based on the documentation: https://pdos.csail.mit.edu/6.828/2016/readings/ia32/ioapic.pdf This code is inspired from the files devices/src/ioapic.rs and devices/src/split_irqchip_common.rs from the crosvm codebase. The reference version used being 6c1e23eee3065b3f3d6fc4fb992ac9884dbabf68. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> 2019-06-12 08:12:45 +00:00			`log = "*"`
cloud-hypervisor: Add devices crate Based on the Firecracker devices crate from commit 9cdb5b2. It is a trimmed down version compared to the Firecracker one, to remove a bunch of pulled dependencies (logger, metrics, rate limiter, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-03-07 13:56:43 +00:00			`vm-memory = { git = "https://github.com/rust-vmm/vm-memory" }`
vendor: Move to the rust-vmm vmm-sys-util package Locked to 60fe35be but no longer dependent on liujing2 repo. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-06-04 11:23:52 +00:00			`vmm-sys-util = { git = "https://github.com/rust-vmm/vmm-sys-util" }`
cloud-hypervisor: Add devices crate Based on the Firecracker devices crate from commit 9cdb5b2. It is a trimmed down version compared to the Firecracker one, to remove a bunch of pulled dependencies (logger, metrics, rate limiter, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-03-07 13:56:43 +00:00
			`[dev-dependencies]`
			`tempfile = ">=3.0.2"`