aboutsummaryrefslogtreecommitdiff
path: root/hw/ppc/spapr_nvdimm.c
diff options
context:
space:
mode:
authorCédric Le Goater <clg@kaod.org>2020-08-20 15:45:47 +0200
committerDavid Gibson <david@gibson.dropbear.id.au>2020-09-08 10:08:42 +1000
commiteab0a2d06e97ebcf74e8437aa985eee5df3a4c68 (patch)
tree46912606a6036ce0051cc880b38d38efe98ce9bb /hw/ppc/spapr_nvdimm.c
parentacbdb9956fe93f4669141f103cb543d3025775db (diff)
downloadqemu-eab0a2d06e97ebcf74e8437aa985eee5df3a4c68.zip
qemu-eab0a2d06e97ebcf74e8437aa985eee5df3a4c68.tar.gz
qemu-eab0a2d06e97ebcf74e8437aa985eee5df3a4c68.tar.bz2
spapr/xive: Allocate vCPU IPIs from the vCPU contexts
When QEMU switches to the XIVE interrupt mode, it creates all the guest interrupts at the level of the KVM device. These interrupts are backed by real HW interrupts from the IPI interrupt pool of the XIVE controller. Currently, this is done from the QEMU main thread, which results in allocating all interrupts from the chip on which QEMU is running. IPIs are not distributed across the system and the load is not well balanced across the interrupt controllers. Change the vCPU IPI allocation to run from the vCPU context. The associated XIVE IPI interrupt will be allocated on the chip on which the vCPU is running and improve distribution of the IPIs in the system. When the vCPUs are pinned, this will make the IPI local to the chip of the vCPU. It will reduce rerouting between interrupt controllers and gives better performance. Device interrupts are still treated the same. To improve placement, we would need some information on the chip owning the virtual source or the HW source in case of a passthrough device but this reuires changes in PAPR. Signed-off-by: Cédric Le Goater <clg@kaod.org> Message-Id: <20200820134547.2355743-5-clg@kaod.org> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'hw/ppc/spapr_nvdimm.c')
0 files changed, 0 insertions, 0 deletions