Michael Zhao 4a51a6615f arch: Fix AArch64 socket setting in CPU topology ... Before Linux v6.0, AArch64 didn't support "socket" in "cpu-map" (CPU topology) of FDT. We found that clusters can be used in the same way of sockets. That is the way we implemented the socket settings in Cloud Hypervisor. But in fact it was a bug. Linux commit 26a2b7 fixed the mistake. So the cluster nodes can no longer act as sockets. And in a following commit dea8c0, sockets were supported. This patch fixed the way to configure sockets. In each socket, a default cluster was added to contain all the cores, because cluster layer is mandatory in CPU topology on AArch64. This fix will break the socket settings on the guests where the kernel version is lower than v6.0. In that case, if socket number is set to more than 1, the kernel will treat that as FDT mistake and all the CPUs will be put in single cluster of single socket. The patch only impacts the case of using FDT, not ACPI. Signed-off-by: Michael Zhao <michael.zhao@arm.com>		2023-01-30 08:12:56 +00:00
..
src	arch: Fix AArch64 socket setting in CPU topology	2023-01-30 08:12:56 +00:00
Cargo.toml	build: Bump thiserror from 1.0.37 to 1.0.38	2023-01-13 01:34:59 +00:00