| commit | 3a4cca14a0a840971410b6e7dd3e1871939d0f03 | [log] [tgz] |
|---|---|---|
| author | Dylan Reid <dgreid@chromium.org> | Thu Jul 13 00:52:05 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Thu Jul 20 22:00:37 2017 |
| tree | 0cdcdaadb3734356323bb32a7d0593b5bffac9f0 | |
| parent | 2cfc2056aae2cf694791705db45cd2f4c2bd5373 [diff] |
crosvm: block - Fill upper 4 bytes of disk size Fill the upper for bytes of the disk size configuration. The size is a 64bit value accessed with two 32bit reads. The guest is permitted to read at any byte offset in the config space. Allow it to do so, even if it doesn't make much sense. Change-Id: I5d02620a8751b31784e419ae6a57173a2e212b8f Signed-off-by: Dylan Reid <dgreid@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/569359 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.