commit | f6a502d760c7eb53111d82bf36b6bcf88cab7712 | [log] [tgz] |
---|---|---|
author | David Dai <davidai@google.com> | Fri Apr 19 20:57:00 2024 +0000 |
committer | David Dai <davidai@google.com> | Tue Apr 30 15:33:44 2024 -0700 |
tree | f47ffc430eb61caa59710d8799ab652cffde3108 | |
parent | 2390b1a47a950f0397862ff50c74e01ca5d9b714 [diff] |
UPSTREAM: Revert "aarch64: Use cpu_capacity to determine clustering instead" This reverts commit b7e72de084373e426a9b5de8535d657c27fd99b4. Reason for revert: It turns out some devices intentionally flattens out their cpu-map topology to improve scheduling behavior. Revert back to using package id to determine clustering info. Original change's description: > aarch64: Use cpu_capacity to determine clustering instead > > Some systems do not populate cpu-map information and > use other ways of grouping CPUs in a frequency/topology > domain instead. Use normalized cpu_capacity information > to determine clustering instead. > > BUG=b:326170473 > Test=./tools/presubmit > Change-Id: If4ba7d224338798fcf2c0ffbaa91547dc2f2e16d > Signed-off-by: David Dai <davidai@google.com> > Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5319790 > Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Test: Boots microdroid with protected mode Bug: b:335130218 Change-Id: I1a601e65a79aacb68c1244127420b2e395f12d5d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5467699 Commit-Queue: David Dai <davidai@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 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.