aboutsummaryrefslogtreecommitdiff
path: root/numa.c
diff options
context:
space:
mode:
authorCédric Le Goater <clg@kaod.org>2019-06-14 18:59:19 +0200
committerDavid Gibson <david@gibson.dropbear.id.au>2019-07-02 09:43:58 +1000
commit981b1c6266c60f4eb86e09ef00f1b5dd046525c7 (patch)
tree410561671d623bdb552af8ed8fd2c5c2a48bca86 /numa.c
parenta2166410ad7434a6830288beb5858b22d5e35ec5 (diff)
downloadqemu-981b1c6266c60f4eb86e09ef00f1b5dd046525c7.zip
qemu-981b1c6266c60f4eb86e09ef00f1b5dd046525c7.tar.gz
qemu-981b1c6266c60f4eb86e09ef00f1b5dd046525c7.tar.bz2
spapr/xive: rework the mapping the KVM memory regions
Today, the interrupt device is fully initialized at reset when the CAS negotiation process has completed. Depending on the KVM capabilities, the SpaprXive memory regions (ESB, TIMA) are initialized with a host MMIO backend or a QEMU emulated backend. This results in a complex initialization sequence partially done at realize and later at reset, and some memory region leaks. To simplify this sequence and to remove of the late initialization of the emulated device which is required to be done only once, we introduce new memory regions specific for KVM. These regions are mapped as overlaps on top of the emulated device to make use of the host MMIOs. Also provide proper cleanups of these regions when the XIVE KVM device is destroyed to fix the leaks. Signed-off-by: Cédric Le Goater <clg@kaod.org> Message-Id: <20190614165920.12670-2-clg@kaod.org> Reviewed-by: Greg Kurz <groug@kaod.org> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'numa.c')
0 files changed, 0 insertions, 0 deletions