| commit | 3cbded2c51574bfdefe8d26a9c6ff235c7330b59 | [log] [tgz] |
|---|---|---|
| author | Zach Reizner <zachr@google.com> | Wed Aug 30 17:07:01 2017 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Fri Sep 01 12:39:18 2017 -0700 |
| tree | 6e891f47d965e42c47c254094b17b6813ca8dd09 | |
| parent | 86fb9567b588a11ed1f7ed2e3223c25fad07cc6f [diff] |
fix armv7a and aarch64 build errors and warnings
BUG=None
TEST=cargo build --target=armv7a-cros-linux-gnueabi &&
cargo build --target=aarch64-cros-linux-gnu
Change-Id: I954c152f3c8086e24c4809dd5aabb5043fdd63af
Reviewed-on: https://chromium-review.googlesource.com/644408
Commit-Ready: Zach Reizner <zachr@chromium.org>
Tested-by: Zach Reizner <zachr@chromium.org>
Reviewed-by: Jason Clinton <jclinton@chromium.org>
Reviewed-by: Stephen Barber <smbarber@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.