| commit | f480f3d024284a947ad736023cdab23dc2de6adb | [log] [tgz] |
|---|---|---|
| author | Daniel Verkamp <dverkamp@chromium.org> | Wed Apr 23 17:12:38 2025 -0700 |
| committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 28 15:47:49 2025 -0700 |
| tree | f91e2e6c7e2eb5fb80455e25d70ceac438b1ec0f | |
| parent | b2cf2fba8bf240bc09cc396fdd677d853b158a62 [diff] |
aarch64: fdt: add GuestMemory reserved regions to /reserved-memory This is a no-op (there are no ReservedMemory regions on aarch64 currently), but it means that we can coalesce regular guest memory with reserved regions in create_memory_node(), which will be used on x86-64 to allow merging the 640KB-1MB hole with the adjacent memory regions. Change-Id: I4defa3a0321bef4509fd509640189b3dceb40d7c Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6486047 Reviewed-by: Dmitry Torokhov <dtor@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 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.