commit | 3c2abaf838cc4defc8eaaf4bce124dba716bee45 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Fri Jan 07 14:13:04 2022 -0800 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Jan 11 22:41:41 2022 +0000 |
tree | 68ac4be65261205b1891b93ee1a9994cc4e01c0e | |
parent | a475cd47547431ea4b448b5003a17fd0e8c13237 [diff] |
aarch64: deduplicate MMIO region calculations The get_high_mmio_base_size() function duplicates and hard-codes the math from get_platform_mmio_base_size(). Since these are both only called in one location now, pull them into get_resource_allocator() so the plat_mmio variables can be used instead of duplicating the math. Also reorder the SystemAllocator::builder() calls so that they are in the same order as the layout of the regions in memory; this makes no functional difference, but it is less confusing to read. BUG=b:210727578 TEST=Boot crosvm on trogdor64 Change-Id: I1238e5b1d412e41d0b4b9be5b93b59fec6598734 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3373451 Reviewed-by: Dmitry Torokhov <dtor@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> 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.