| commit | d02c3da8a9181f655c9c8e4bfaff357556b036a4 | [log] [tgz] |
|---|---|---|
| author | Daniel Verkamp <dverkamp@chromium.org> | Mon Dec 12 14:20:17 2022 -0800 |
| committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 13 22:32:18 2022 +0000 |
| tree | 608ddfd34e0ec9b1cd769a010d09d3a686d887c5 | |
| parent | 03b165327677640f4395403da9f8314c3f70978c [diff] |
devices: virtio: vsock: move consts to device_constants Avoid the need to import private bits of the vsock device implementation from other modules. BUG=b:262291811 TEST=tools/presubmit --all Change-Id: Ifab1110002f871ac3afa53984daf8223d44d665c Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4098572 Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
crosvm is a virtual machine monitor (VMM) based on Linux’s KVM hypervisor, with a focus on simplicity, security, and speed. crosvm is intended to run Linux guests, originally as a security boundary for running native applications on the Chrome OS platform. Compared to QEMU, crosvm doesn’t emulate architectures or real hardware, instead concentrating on paravirtualized devices, such as the virtio standard.
crosvm is currently used to run Linux/Android guests on Chrome OS devices.