commit | 5586ff508c7032d41e0f0f1d6ba603ad19face95 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Thu Feb 24 16:34:55 2022 -0800 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Mar 09 20:53:38 2022 +0000 |
tree | b13ef56cf4731f1fa704d44b0909a7fec7e37213 | |
parent | de4d729c39e86e90f289878f5fccd33191625710 [diff] |
linux: punch holes in guest memory for file mappings Rather than manually adding special handling for regions where we want to put --file-backed-mapping mappings, we can just iterate over those regions before constructing the GuestMemory object so that there will be no conflicts/overlaps between RAM and file-backed mappings. BUG=b:188011323 TEST=Boot volteer-manatee and brya-manatee Change-Id: I986f33460fa45cd1f85d849810e1f6934cc73c0d Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3489809 Reviewed-by: Junichi Uekawa <uekawa@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Mattias Nissler <mnissler@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.