commit | 379dd2dfecf1a0c06adf0f6e257a5ebc75374cb8 | [log] [tgz] |
---|---|---|
author | Andrew Walbran <qwandor@google.com> | Wed May 04 16:10:45 2022 +0100 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 17 10:08:53 2022 +0000 |
tree | d8fa68d7f774f6add88fd5ba2743503b5e6072ba | |
parent | 3fcf6e68eb0a88dadeff89c48e4ecc9958967d48 [diff] |
Allocate pVM firmware memory consistently. Allocate the same way as the rest of RAM, whether in unprotected-with-firmware mode or actually protected mode. TEST=tools/dev_container tools/run_tests --target=vm:aarch64 Change-Id: Ic0ebc0d90e91bd450af55f3252039ddab8d26443 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3827215 Commit-Queue: Andrew Walbran <qwandor@google.com> Tested-by: Andrew Walbran <qwandor@google.com> Reviewed-by: 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.