aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/qapi/source.py
diff options
context:
space:
mode:
authorGavin Shan <gshan@redhat.com>2023-07-21 20:44:37 +1000
committerPeter Maydell <peter.maydell@linaro.org>2024-01-12 14:02:23 +0000
commit393d5c5bc717b18cd361b4a1ffbfe2a18b29a03b (patch)
treebe374fd1d87f1edca13923f38a3cdbbb41cfe45d /scripts/qapi/source.py
parentMerge tag 'firmware/edk2-20231213-pull-request' of https://gitlab.com/kraxel/qemu into staging (diff)
downloadqemu-393d5c5bc717b18cd361b4a1ffbfe2a18b29a03b.tar.xz
qemu-393d5c5bc717b18cd361b4a1ffbfe2a18b29a03b.zip
numa: Skip invalidation of cluster and NUMA node boundary for qtest
There are warning messages printed from tests/qtest/numa-test.c, to complain the CPU cluster and NUMA node boundary is broken. Since the broken boundary is expected, we don't want to see the warning messages. # cd /home/gavin/sandbox/qemu.main/build # MALLOC_PERTURB_=255 QTEST_QEMU_BINARY=./qemu-system-aarch64 \ G_TEST_DBUS_DAEMON=../tests/dbus-vmstate-daemon.sh \ QTEST_QEMU_IMG=./qemu-img \ QTEST_QEMU_STORAGE_DAEMON_BINARY=./storage-daemon/qemu-storage-daemon \ tests/qtest/numa-test --tap -k : qemu-system-aarch64: warning: CPU-0 and CPU-4 in socket-0-cluster-0 \ have been associated with node-0 and node-1 respectively. \ It can cause OSes like Linux to misbehave : Skip the invalidation of CPU cluster and NUMA node boundary when qtest is enabled, to avoid the warning messages. Fixes: a494fdb715 ("numa: Validate cluster and NUMA node boundary if required") Signed-off-by: Gavin Shan <gshan@redhat.com> Reviewed-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Diffstat (limited to 'scripts/qapi/source.py')
0 files changed, 0 insertions, 0 deletions