summaryrefslogtreecommitdiffstats
path: root/hw/intc/omap_intc.c
diff options
context:
space:
mode:
authorGreg Kurz2019-10-22 18:38:07 +0200
committerDavid Gibson2019-10-24 04:32:33 +0200
commitd1f2b4691a268306a319ea76f67421431f529a07 (patch)
tree03ec5acb9f590b51e05372495a184f762ceda5f0 /hw/intc/omap_intc.c
parentspapr: move CPU reset after presenter creation (diff)
downloadqemu-d1f2b4691a268306a319ea76f67421431f529a07.tar.gz
qemu-d1f2b4691a268306a319ea76f67421431f529a07.tar.xz
qemu-d1f2b4691a268306a319ea76f67421431f529a07.zip
spapr_cpu_core: Implement DeviceClass::reset
Since vCPUs aren't plugged into a bus, we manually register a reset handler for each vCPU. We also call this handler at realize time to ensure hot plugged vCPUs are reset before being exposed to the guest. This results in vCPUs being reset twice at machine reset. It doesn't break anything but it is slightly suboptimal and above all confusing. The hotplug path in device_set_realized() already knows how to reset a hotplugged device if the device reset handler is present. Implement one for sPAPR CPU cores that resets all vCPUs under a core. While here rename spapr_cpu_reset() to spapr_reset_vcpu() for consistency with spapr_realize_vcpu() and spapr_unrealize_vcpu(). Signed-off-by: Greg Kurz <groug@kaod.org> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com> [clg: add documentation on the reset helper usage ] Signed-off-by: Cédric Le Goater <clg@kaod.org> Message-Id: <20191022163812.330-3-clg@kaod.org> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'hw/intc/omap_intc.c')
0 files changed, 0 insertions, 0 deletions