Gavin Shan a494fdb715 numa: Validate cluster and NUMA node boundary if required ... For some architectures like ARM64, multiple CPUs in one cluster can be associated with different NUMA nodes, which is irregular configuration because we shouldn't have this in baremetal environment. The irregular configuration causes Linux guest to misbehave, as the following warning messages indicate. -smp 6,maxcpus=6,sockets=2,clusters=1,cores=3,threads=1 \ -numa node,nodeid=0,cpus=0-1,memdev=ram0 \ -numa node,nodeid=1,cpus=2-3,memdev=ram1 \ -numa node,nodeid=2,cpus=4-5,memdev=ram2 \ ------------[ cut here ]------------ WARNING: CPU: 0 PID: 1 at kernel/sched/topology.c:2271 build_sched_domains+0x284/0x910 Modules linked in: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.14.0-268.el9.aarch64 #1 pstate: 00400005 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : build_sched_domains+0x284/0x910 lr : build_sched_domains+0x184/0x910 sp : ffff80000804bd50 x29: ffff80000804bd50 x28: 0000000000000002 x27: 0000000000000000 x26: ffff800009cf9a80 x25: 0000000000000000 x24: ffff800009cbf840 x23: ffff000080325000 x22: ffff0000005df800 x21: ffff80000a4ce508 x20: 0000000000000000 x19: ffff000080324440 x18: 0000000000000014 x17: 00000000388925c0 x16: 000000005386a066 x15: 000000009c10cc2e x14: 00000000000001c0 x13: 0000000000000001 x12: ffff00007fffb1a0 x11: ffff00007fffb180 x10: ffff80000a4ce508 x9 : 0000000000000041 x8 : ffff80000a4ce500 x7 : ffff80000a4cf920 x6 : 0000000000000001 x5 : 0000000000000001 x4 : 0000000000000007 x3 : 0000000000000002 x2 : 0000000000001000 x1 : ffff80000a4cf928 x0 : 0000000000000001 Call trace: build_sched_domains+0x284/0x910 sched_init_domains+0xac/0xe0 sched_init_smp+0x48/0xc8 kernel_init_freeable+0x140/0x1ac kernel_init+0x28/0x140 ret_from_fork+0x10/0x20 Improve the situation to warn when multiple CPUs in one cluster have been associated with different NUMA nodes. However, one NUMA node is allowed to be associated with different clusters. Signed-off-by: Gavin Shan <gshan@redhat.com> Acked-by: Philippe Mathieu-Daudé <philmd@linaro.org> Acked-by: Igor Mammedov <imammedo@redhat.com> Message-Id: <20230509002739.18388-2-gshan@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2023-06-26 10:23:01 +02:00
..
bus.c
clock-vmstate.c
clock.c
cpu-common.c	hw/core/cpu: Simplify realize() using MACHINE_GET_CLASS() macro	2023-06-09 23:38:16 +03:00
cpu-sysemu.c
fw-path-provider.c
generic-loader.c
gpio.c
guest-loader.c
guest-loader.h
hotplug-stubs.c
hotplug.c
irq.c
Kconfig
loader-fit.c
loader.c	*: Add missing includes of qemu/error-report.h	2023-03-22 15:06:57 +00:00
machine-hmp-cmds.c
machine-qmp-cmds.c	hw/core: Move machine-qmp-cmds.c into the target independent source set	2023-05-16 09:14:18 +02:00
machine-smp.c	*: Add missing includes of qemu/error-report.h	2023-03-22 15:06:57 +00:00
machine.c	numa: Validate cluster and NUMA node boundary if required	2023-06-26 10:23:01 +02:00
meson.build	meson: Replace softmmu_ss -> system_ss	2023-06-20 10:01:30 +02:00
nmi.c
null-machine.c
numa.c	numa: Check for qemu_strtosz_MiB error	2023-06-02 12:29:27 -05:00
or-irq.c	hw: Replace qemu_or_irq typedef by OrIRQState	2023-02-27 13:27:05 +00:00
platform-bus.c
ptimer.c	replay: Extract core API to 'exec/replay-core.h'	2023-02-27 22:29:01 +01:00
qdev-clock.c
qdev-fw.c
qdev-hotplug.c
qdev-prop-internal.h
qdev-properties-system.c
qdev-properties.c
qdev.c	hw/qdev: Constify DeviceState* argument of qdev_get_parent_bus()	2023-02-27 22:29:01 +01:00
register.c
reset.c
resettable.c
split-irq.c
stream.c
sysbus-fdt.c
sysbus.c
trace-events	trace-events: remove the remaining vcpu trace events	2023-06-01 11:05:05 -04:00
trace.h
uboot_image.h
vm-change-state-handler.c
vmstate-if.c