cloud-hypervisor/arch/Cargo.toml

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

[dependencies]
byteorder = "=1.2.1"
kvm-bindings = "0.1"
kvm-ioctls = { git = "https://github.com/rust-vmm/kvm-ioctls", branch = "master" }
libc = ">=0.2.39"

arch_gen = { path = "../arch_gen" }

[dependencies.vm-memory]
git = "https://github.com/rust-vmm/vm-memory"
features = ["backend-mmap"]

[dev-dependencies]
rand = ">=0.5.5"
cloud-hypervisor: Add the architecture crates Both crates are based on Firecracker commit 9cdb5b2. They are ported to the new memory model and tests have been fixed accordingly. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-02-25 21:53:01 +00:00			`[package]`
			`name = "arch"`
			`version = "0.1.0"`
			`authors = ["The Chromium OS Authors"]`

			`[dependencies]`
			`byteorder = "=1.2.1"`
			`kvm-bindings = "0.1"`
dep: Rely on latest kvm-ioctls crate In order to have access to the newly added signal_msi() function from the kvm-ioctls crate, this commit updates the version of the kvm-ioctls to the latest one. Because set_user_memory_region() has been swtiched to "unsafe", we also need to handle this small change in our cloud-hypervisor code directly. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> 2019-06-03 21:09:01 +00:00			`kvm-ioctls = { git = "https://github.com/rust-vmm/kvm-ioctls", branch = "master" }`
cloud-hypervisor: Add the architecture crates Both crates are based on Firecracker commit 9cdb5b2. They are ported to the new memory model and tests have been fixed accordingly. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-02-25 21:53:01 +00:00			`libc = ">=0.2.39"`

			`arch_gen = { path = "../arch_gen" }`

			`[dependencies.vm-memory]`
			`git = "https://github.com/rust-vmm/vm-memory"`
			`features = ["backend-mmap"]`

			`[dev-dependencies]`
			`rand = ">=0.5.5"`