commit | 09a95f5e74c47d43a1f6962fca108466d8cc31e5 | [log] [tgz] |
---|---|---|
author | Zach Reizner <zachr@google.com> | Wed Aug 02 14:08:29 2017 -0700 |
committer | chrome-bot <chrome-bot@chromium.org> | Sat Aug 05 22:07:53 2017 -0700 |
tree | b99352962c0edcea90fa36dc39641d4b15f8c477 | |
parent | 7a9de27c36b9a5ea3e29b3508939c20e6a5c7779 [diff] |
kvm: add device memory interface to Vm This interface is to dynamically add and remove memory mappings to guest physical address space. TEST=cargo test BUG=chromium:738638 Change-Id: I695775289d56686ef16a1e3cf7640c97d5da2662 Reviewed-on: https://chromium-review.googlesource.com/599040 Commit-Ready: Zach Reizner <zachr@chromium.org> Tested-by: Zach Reizner <zachr@chromium.org> Reviewed-by: Dylan Reid <dgreid@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.