| commit | 56b11587dfc79dc6453d857159801dcc38f24d0c | |
| author | Cédric Le Goater <clg@kaod.org> | |
| Mon, 13 May 2019 08:42:40 +0000 (13 10:42 +0200) | ||
| committer | David Gibson <david@gibson.dropbear.id.au> | |
| Wed, 29 May 2019 01:39:46 +0000 (29 11:39 +1000) | ||
| tree | ffc58f0552cf01c0c09494b534bf2b3347137fcb | treesnapshot (tar.gz zip) |
| parent | 90c20e1e2ce0fb52975ff4d6590620ef0129790e | commitdiff |
spapr: introduce routines to delete the KVM IRQ device
If a new interrupt mode is chosen by CAS, the machine generates a
reset to reconfigure. At this point, the connection with the previous
KVM device needs to be closed and a new connection needs to opened
with the KVM device operating the chosen interrupt mode.
New routines are introduced to destroy the XICS and the XIVE KVM
devices. They make use of a new KVM device ioctl which destroys the
device and also disconnects the IRQ presenters from the vCPUs.
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Message-Id: <20190513084245.25755-10-clg@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
If a new interrupt mode is chosen by CAS, the machine generates a
reset to reconfigure. At this point, the connection with the previous
KVM device needs to be closed and a new connection needs to opened
with the KVM device operating the chosen interrupt mode.
New routines are introduced to destroy the XICS and the XIVE KVM
devices. They make use of a new KVM device ioctl which destroys the
device and also disconnects the IRQ presenters from the vCPUs.
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Message-Id: <20190513084245.25755-10-clg@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
| hw/intc/spapr_xive_kvm.c | diffblobblamehistory | |
| hw/intc/xics_kvm.c | diffblobblamehistory | |
| include/hw/ppc/spapr_xive.h | diffblobblamehistory | |
| include/hw/ppc/xics_spapr.h | diffblobblamehistory |