| commit | bf36bcbc4a843279aebff26666a5ca802a7b37fb | [log] [tgz] |
|---|---|---|
| author | Zach Reizner <zachr@google.com> | Fri Jul 07 00:59:49 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Fri Jul 21 04:21:29 2017 |
| tree | 45e55132950ca29c48945723c91c80ed0fba4fe4 | |
| parent | 3a4cca14a0a840971410b6e7dd3e1871939d0f03 [diff] |
sys_util: add sock_ctrl_msg module for transmitting messages with FD This CL also includes the gcc build time dependency for building the sock_ctrl_msg.c helper code. TEST=cargo test BUG=chromium:738638 Change-Id: I4adc2360b7fab4ed7d557603aa7bad2e738b69b4 Reviewed-on: https://chromium-review.googlesource.com/562574 Commit-Ready: Zach Reizner <zachr@chromium.org> Tested-by: Zach Reizner <zachr@chromium.org> Reviewed-by: Chirantan Ekbote <chirantan@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.