commit | dddf3b4863ac285fdfa5d1c9e1269cee97c9644a | [log] [tgz] |
---|---|---|
author | Elliot Berman <quic_eberman@quicinc.com> | Mon Apr 10 15:43:25 2023 -0700 |
committer | Frederick Mayle <fmayle@google.com> | Fri May 12 22:02:29 2023 +0000 |
tree | fbc9d7eb8fdce03eef8d44136fea8672c6b1b8a9 | |
parent | 59bd2db468a8a6b3cb81000354c4a9f035a17837 [diff] |
hypervisor: gunyah: Remove push-compatible for StaticSwiotlbRegion "restricted-dma-pool" was added to the shm-node as a workaround during initial development of AVF. This workaround is no longer needed and not used in any deployed devices, so remove it. BUG=b:232360323 Signed-off-by: Elliot Berman <quic_eberman@quicinc.com> (cherry picked from commit 184c747bd4e8a93802619efff0f3815c8a23daaa) Change-Id: I08e1335992af58b0075d77e1da227851ecd8e0e1 Bug: 232360323 Ignore-AOSP-First: Already in AOSP
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 ChromeOS 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 ChromeOS devices.