mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-01-27 02:28:22 +00:00
No description
045c7133dd
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> |
||
|---|---|---|
| data_model | ||
| io_jail | ||
| kernel_loader | ||
| kvm | ||
| kvm_sys | ||
| src/hw | ||
| sys_util | ||
| syscall_defines | ||
| x86_64 | ||
| .gitignore | ||
| LICENSE | ||
| README.md | ||
Chrome OS KVM
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.
Overview
The crosvm source code is organized into crates, each with their own unit tests. These crates are:
kvm-syslow-level (mostly) auto-generated structures and constants for using KVMkvmunsafe, low-level wrapper code for using kvm-syscrosvmthe top-level binary front-end for using crosvm
Usage
Currently there is no front-end, so the best you can do is run cargo test in
each crate.