This series addresses the same aspects on PPC the bug 1103314 addressed
on x86. It sets the target numa node in the pci-root instead of
using the pci-expander-bus.
The patch 2 & 3 were sent earlier and was suggested to wait for the multi-phb
support. Here, https://www.redhat.com/archives/libvir-list/2016-November/msg00403.html
Now that multi-phb support is in, this version takes the multi-phb scenarios
into account. Specifying NUMA node for the default PHB is prevented and let
me know if that should be allowed. Patch 3 has more details.
Relavent discussion :
https://www.redhat.com/archives/libvir-list/2017-July/msg00383.html
---
Shivaprasad G Bhat (3):
Add capabilities for qemu-2.9.0 ppc64
qemu: capabilitity: Introduce QEMU_CAPS_SPAPR_PCI_HOST_BRIDGE_NUMA_NODE
qemu: Enable NUMA node tag in pci-root for PPC64
docs/formatdomain.html.in | 5
src/conf/domain_conf.c | 6
src/qemu/qemu_capabilities.c | 8
src/qemu/qemu_capabilities.h | 1
src/qemu/qemu_command.c | 10
src/qemu/qemu_domain.c | 9
.../caps_2.6.0.ppc64le.replies | 60
.../caps_2.9.0.ppc64le.replies |19274 ++++++++++++++++++++
tests/qemucapabilitiesdata/caps_2.9.0.ppc64le.xml | 1063 +
tests/qemucapabilitiestest.c | 1
...muxml2argv-spapr-pci-host-bridge-numa-node.args | 29
...emuxml2argv-spapr-pci-host-bridge-numa-node.xml | 54
tests/qemuxml2argvtest.c | 3
13 files changed, 20514 insertions(+), 9 deletions(-)
create mode 100644 tests/qemucapabilitiesdata/caps_2.9.0.ppc64le.replies
create mode 100644 tests/qemucapabilitiesdata/caps_2.9.0.ppc64le.xml
create mode 100644 tests/qemuxml2argvdata/qemuxml2argv-spapr-pci-host-bridge-numa-node.args
create mode 100644 tests/qemuxml2argvdata/qemuxml2argv-spapr-pci-host-bridge-numa-node.xml
--
Signature
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list