| commit | 045c7133dd22e4cc5fe62af136c15b04a8b8a485 | [log] [tgz] |
|---|---|---|
| author | Dylan Reid <dgreid@chromium.org> | Tue Jun 20 20:44:40 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Mon Jun 26 22:28:36 2017 |
| tree | 7ff0f5b65f2e45f84ffe70dfece3c1a76809d506 | |
| parent | be4a4c97be4afa6ac4808808841a97bdf5661e04 [diff] |
Add data_model with DataInit trait The data_model crate is created to hold the DataInit trait. Types implementing this unsafe trait must guarantee that the type can be initialized with random data and the resulting object will be valid. Change-Id: Id6314d114805ec502adabe50a8bd6aa42fdb2c52 Signed-off-by: Dylan Reid <dgreid@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/541681 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.