summaryrefslogtreecommitdiff
path: root/trace/control-target.c
diff options
context:
space:
mode:
authorGreg Kurz <groug@kaod.org>2020-02-24 20:23:43 +0100
committerDavid Gibson <david@gibson.dropbear.id.au>2020-03-17 09:41:14 +1100
commitad334d89a695460ca1387d96bb8ab7aef0909df4 (patch)
tree7149771b5857753be74ce98f1f142951f5d00b9b /trace/control-target.c
parentf350d78f102faef84910733b6c45e2c72a05d86a (diff)
downloadqemu-ad334d89a695460ca1387d96bb8ab7aef0909df4.zip
spapr: Handle pending hot plug/unplug requests at CAS
If a hot plug or unplug request is pending at CAS, we currently trigger a CAS reboot, which severely increases the guest boot time. This is because SLOF doesn't handle hot plug events and we had no way to fix the FDT that gets presented to the guest. We can do better thanks to recent changes in QEMU and SLOF: - we now return a full FDT to SLOF during CAS - SLOF was fixed to correctly detect any device that was either added or removed since boot time and to update its internal DT accordingly. The right solution is to process all pending hot plug/unplug requests during CAS: convert hot plugged devices to cold plugged devices and remove the hot unplugged ones, which is exactly what spapr_drc_reset() does. Also clear all hot plug events that are currently queued since they're no longer relevant. Note that SLOF cannot currently populate hot plugged PCI bridges or PHBs at CAS. Until this limitation is lifted, SLOF will reset the machine when this scenario occurs : this will allow the FDT to be fully processed when SLOF is started again (ie. the same effect as the CAS reboot that would occur anyway without this patch). Signed-off-by: Greg Kurz <groug@kaod.org> Message-Id: <158257222352.4102917.8984214333937947307.stgit@bahia.lan> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'trace/control-target.c')
0 files changed, 0 insertions, 0 deletions