| commit | d527d85da64ff265a8091fc9129244e02f994f0a | [log] [tgz] |
|---|---|---|
| author | Dylan Reid <dgreid@chromium.org> | Thu Aug 10 21:58:34 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Tue Aug 15 01:24:55 2017 |
| tree | 3addedc952bd5b753933957a7e52a7c623d6534a | |
| parent | c28f6a67b16d2bb8e113bfd09ec8238069fa14c0 [diff] |
crosvm: Add barrier before updating used_ring index We have to guarantee that all the descriptor writes are visible to the guest before the index update is. Change-Id: I35f1c8d3f5fc9a6ac54de1eb4be66e1c5ac81fc8 Signed-off-by: Dylan Reid <dgreid@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/611215 Reviewed-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.