mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2024-12-28 06:27:13 +00:00
No description
56158c873a
These functions are trivially safe and by adding them to sys_util, we
can remove some unsafe blocks from crosvm. This CL also replaces the
unsafe call sites with the safe alternatives.
There are no previous usages of gete{g,u}id(2), but they will be needed
in a future change.
TEST=None
BUG=None
Change-Id: Ief8787b298cfaa5b7fd1b83f0eba6660369e687d
Reviewed-on: https://chromium-review.googlesource.com/634268
Commit-Ready: Zach Reizner <zachr@chromium.org>
Tested-by: Zach Reizner <zachr@chromium.org>
Reviewed-by: Dylan Reid <dgreid@chromium.org>
|
||
|---|---|---|
| data_model | ||
| io_jail | ||
| kernel_loader | ||
| kvm | ||
| kvm_sys | ||
| net_sys | ||
| net_util | ||
| seccomp/x86_64 | ||
| src | ||
| sys_util | ||
| syscall_defines | ||
| vhost | ||
| virtio_sys | ||
| x86_64 | ||
| .gitignore | ||
| Cargo.toml | ||
| 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:
kernel_loaderLoads elf64 kernel files to a slice of memory.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 crosvmx86_64Support code specific to 64 bit intel machines.
Usage
Currently there is no front-end, so the best you can do is run cargo test in
each crate.