commit | 2cd328fdf17c1bf0f979bf4c728538f6edb0761e | [log] [tgz] |
---|---|---|
author | Frederick Mayle <fmayle@google.com> | Mon Nov 28 22:32:12 2022 -0800 |
committer | Frederick Mayle <fmayle@google.com> | Tue Nov 29 23:12:27 2022 +0000 |
tree | 654c391a6c77c02d72e2d52b65eb6e1a042ef3a9 | |
parent | e334d8997dd1d8b089de8c2c9f55bbd5b7f04e53 [diff] |
ANDROID: Verify virtio queue address ranges are valid Partial backport of https://crrev.com/c/3945520 Excluded the x86_64 changes because I believe they are redundant. Excluded the ipc_memory_mapper.rs changes because they are not applicable to the target branch (there are no direct guest memory accesses in that module). Bug: 251802307 Test: TH Change-Id: I75ab20d1a96f26326cd2d87586cd93e4bf53971c Merged-In: I21bce5d1c60acdff79284cdad963849a6e19e19c Merged-In: Id9a7b8b469247992afd98fe80593c5044c112406
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.