| commit | 303f86fa21dd2ac21076da29dbc8957516724781 | [log] [tgz] |
|---|---|---|
| author | Dylan Reid <dgreid@chromium.org> | Tue May 02 01:22:11 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Tue May 02 12:20:27 2017 |
| tree | 289c7d76d6be19369cbe2b922d6ea9397b5f7611 | |
| parent | bf86e0fc86d7bf8b11804a2e89c174798259beee [diff] |
kvm-sys: rename to kvm_sys underscores are better Change-Id: Ida36de419f6ecf704f40d868cf7296d4d4fc41e6 Reviewed-on: https://chromium-review.googlesource.com/492666 Commit-Ready: Zach Reizner <zachr@chromium.org> Tested-by: Zach Reizner <zachr@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:
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 crosvmCurrently there is no front-end, so the best you can do is run cargo test in each crate.