mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2024-11-25 05:03:05 +00:00
8a72afc44c
The --cpu-cluster option can be used to report a physical grouping of CPUs in the device tree as a "cpu-map" node: https://www.kernel.org/doc/Documentation/devicetree/bindings/arm/topology.txt Each instance of the --cpu-cluster option specifies a new group consisting of a list of CPUs, and it may be repeated to add multiple groups. The --cpu-capacity option can be used to specify the relative performance of CPUs so that the guest kernel's scheduler can make better decisions on systems with heterogeneous cores (e.g. big.LITTLE). --cpu-capacity units are left up to each architecture; for devicetree systems, capacity is used to fill the cpu capacity-dmips-mhz (Dhrystone benchmark MIPS per MHz) field in each cpu node: https://www.kernel.org/doc/Documentation/devicetree/bindings/arm/cpu-capacity.txt For example, on a trogdor board, there are 6 little cores (0-5) with a capacity of 452, and 2 big cores (6-7) with a capacity of 1024, which results in a crosvm command line argument of: --cpu-capacity 0-452,1=452,2=452,3=452,4=452,5=452,6=1024,7=1024 Currently, these options only have an effect on devicetree platforms and are ignored elsewhere; they may be expanded in the future to fill in the equivalent ACPI tables if systems with heterogeneous CPUs are used there. BUG=b:182198842 TEST=Start crosvm on kevin with --cpu-cluster options TEST=crosvm run --cpu-cluster 0,1,2,3 --cpu-cluster 4,5 Change-Id: I59c466549ccd908f8eea1da0651d82716bc82972 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2762298 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> |
||
|---|---|---|
| .. | ||
| src | ||
| .build_test_skip | ||
| Cargo.toml | ||