diff options
author | Greg Kurz <groug@kaod.org> | 2019-10-24 16:27:22 +0200 |
---|---|---|
committer | Laurent Vivier <lvivier@redhat.com> | 2019-11-18 11:49:11 +0100 |
commit | 0990ce6a2e900d0bdda7f3ecdc991746f63551fb (patch) | |
tree | 38bc8fa17c3a2477949aabb8fc852c45795fe1e7 /hw/intc/xive.c | |
parent | 36609b4fa36f0ac934874371874416f7533a5408 (diff) | |
download | qemu-0990ce6a2e900d0bdda7f3ecdc991746f63551fb.zip qemu-0990ce6a2e900d0bdda7f3ecdc991746f63551fb.tar.gz qemu-0990ce6a2e900d0bdda7f3ecdc991746f63551fb.tar.bz2 |
ppc: Add intc_destroy() handlers to SpaprInterruptController/PnvChip
SpaprInterruptControllerClass and PnvChipClass have an intc_create() method
that calls the appropriate routine, ie. icp_create() or xive_tctx_create(),
to establish the link between the VCPU and the presenter component of the
interrupt controller during realize.
There aren't any symmetrical call to be called when the VCPU gets unrealized
though. It is assumed that object_unparent() is the only thing to do.
This is questionable because the parenting logic around the CPU and
presenter objects is really an implementation detail of the interrupt
controller. It shouldn't be open-coded in the machine code.
Fix this by adding an intc_destroy() method that undoes what was done in
intc_create(). Also NULLify the presenter pointers to avoid having
stale pointers around. This will allow to reliably check if a vCPU has
a valid presenter.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <157192724208.3146912.7254684777515287626.stgit@bahia.lan>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Laurent Vivier <lvivier@redhat.com>
Diffstat (limited to 'hw/intc/xive.c')
-rw-r--r-- | hw/intc/xive.c | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/hw/intc/xive.c b/hw/intc/xive.c index f066be5..38257aa 100644 --- a/hw/intc/xive.c +++ b/hw/intc/xive.c @@ -696,6 +696,11 @@ error: return NULL; } +void xive_tctx_destroy(XiveTCTX *tctx) +{ + object_unparent(OBJECT(tctx)); +} + /* * XIVE ESB helpers */ |