commit | fc8bb6efbfaac7b11eb7059e9ae342ab25a32fa8 | [log] [tgz] |
---|---|---|
author | Andrew Walbran <qwandor@google.com> | Tue Sep 27 16:19:33 2022 +0100 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 20 10:23:20 2023 +0000 |
tree | 57f7da0de3e274b31e07aa71987353afa2424e89 | |
parent | 03c46712333f76afcc63c88d481d7974549712fa [diff] |
aarch64: Merge adjacent regions in FDT memory node. BUG=b:244553205 TEST=Patched into AOSP and ran some VMs. Change-Id: I95710fdb264a3bd1e8e69ed6dfad77bbc05b3043 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4440589 Reviewed-by: Jiyong Park <jiyong@google.com> Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Pierre-Clément Tosi <ptosi@google.com> Commit-Queue: Andrew Walbran <qwandor@google.com>
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.