Hi Peter and maintainers, On 4/25/22 11:27 AM, Gavin Shan wrote:
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/5] Add cluster-id to CPU instance property PATCH[2/5] Fixes test failure in qtest/numa-test/aarch64_numa_cpu() PATCH[3/5] Uses SMP configuration to populate CPU topology PATCH[4/5] Fixes the broken CPU topology by considering the socket boundary when the default NUMA node ID is given PATCH[5/5] Uses the populated CPU topology to build PPTT table, instead of calculate it again
Could you help to check if it's eligible for 7.1? Thanks a lot for your comments in advance. [...]
Gavin Shan (5): qapi/machine.json: Add cluster-id qtest/numa-test: Specify CPU topology in aarch64_numa_cpu() 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/acpi/aml-build.c | 111 ++++++++++++++++--------------------- hw/arm/virt.c | 19 ++++++- hw/core/machine-hmp-cmds.c | 4 ++ hw/core/machine.c | 16 ++++++ qapi/machine.json | 6 +- tests/qtest/numa-test.c | 3 +- 6 files changed, 91 insertions(+), 68 deletions(-)
Thanks, Gavin
