When the CPU-to-NUMA association isn't provided by user, the default NUMA
node ID for the specific CPU is returned from virt_get_default_cpu_node_id().
Unfortunately, the default NUMA node ID breaks socket boundary and leads to
the broken CPU topology warning message in Linux guest. This series intends
to fix the issue.
PATCH[1/4] Uses SMP configuration to populate CPU topology
PATCH[2/4] Fixes the broken CPU topology by considering the socket boundary
when the default NUMA node ID is given
PATCH[3/4] Uses the populated CPU topology to build PPTT table, instead of
calculate it again
PATCH[4/4] Take thread ID as the ACPI processor ID in MDAT and SRAT tables
Changelog
=========
v3:
* Split PATCH[v2 1/3] to PATCH[v3 1/4] and PATCH[v3 2/4] (Yanan)
* Don't take account of die ID in CPU topology population
and added assert(!mc->smp_props.dies_supported) (Yanan/Igor)
* Assign cluster_id and use it when building PPTT table (Yanan/Igor)
v2:
* Populate the CPU topology in virt_possible_cpu_arch_ids()
so that it can be reused in virt_get_default_cpu_node_id() (Igor)
* Added PATCH[2/3] to use the existing CPU topology when the
PPTT table is built (Igor)
* Added PATCH[3/3] to take thread ID as ACPI processor ID
in MADT and SRAT table (Gavin)
Gavin Shan (4):
hw/arm/virt: Consider SMP configuration in CPU topology
hw/arm/virt: Fix CPU's default NUMA node ID
hw/acpi/aml-build: Use existing CPU topology to build PPTT table
hw/arm/virt: Unify ACPI processor ID in MADT and SRAT table
hw/acpi/aml-build.c | 96 ++++++++++++++++++++++++++++++----------
hw/arm/virt-acpi-build.c | 12 +++--
hw/arm/virt.c | 15 ++++++-
qapi/machine.json | 6 ++-
4 files changed, 99 insertions(+), 30 deletions(-)
--
2.23.0
