| commit | 8686d9ff5b11d3b72be1d05cff4bc62e41a02db7 | [log] [tgz] |
|---|---|---|
| author | Stephen Barber <smbarber@chromium.org> | Wed Jun 21 15:04:16 2017 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Thu Jul 13 22:03:30 2017 -0700 |
| tree | 8280d49244ddfc0fafd29770cac39e8f4efad740 | |
| parent | 861d672430ad1383cf7a46de9aad399d391580ff [diff] |
crosvm: refactor mmio device setup In preparation for adding a net device, factor out some of the common code for setting up an mmio device and jailing it. Signed-off-by: Stephen Barber <smbarber@chromium.org> BUG=none TEST=cargo test Change-Id: I94f02e56a2b0938d860322b731d8b17a25357128 Reviewed-on: https://chromium-review.googlesource.com/543910 Commit-Ready: Stephen Barber <smbarber@chromium.org> Tested-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org>
This component, known as crosvm, runs untrusted operating systems along with virtualized devices. No actual hardware is emulated. This only runs VMs through the Linux's KVM interface. What makes crosvm unique is a focus on safety within the programming language and a sandbox around the virtual devices to protect the kernel from attack in case of an exploit in the devices.
The crosvm source code is organized into crates, each with their own unit tests. These crates are:
kernel_loader Loads elf64 kernel files to a slice of memory.kvm_sys low-level (mostly) auto-generated structures and constants for using KVMkvm unsafe, low-level wrapper code for using kvm_syscrosvm the top-level binary front-end for using crosvmx86_64 Support code specific to 64 bit intel machines.Currently there is no front-end, so the best you can do is run cargo test in each crate.