| commit | 5dd5238c0b5cc42d347128227f124fe31b05832d | |
| author | Jianjun Duan <duanj@linux.vnet.ibm.com> | |
| Tue, 24 May 2016 17:55:04 +0000 (24 10:55 -0700) | ||
| committer | David Gibson <david@gibson.dropbear.id.au> | |
| Thu, 26 May 2016 23:40:23 +0000 (27 09:40 +1000) | ||
| tree | 9b9165a9f0d12767ced92c4319e4b83564723a9f | treesnapshot (tar.gz zip) |
| parent | 41264b385c2b324fea026204e5de9bef980733b1 | commitdiff |
spapr: ensure device trees are always associated with DRC
There are possible racing situations involving hotplug events and
guest migration. For cases where a hotplug event is migrated, or
the guest is in the process of fetching device tree at the time of
migration, we need to ensure the device tree is created and
associated with the corresponding DRC for devices that were
hotplugged on the source, but 'coldplugged' on the target.
Signed-off-by: Jianjun Duan <duanj@linux.vnet.ibm.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
There are possible racing situations involving hotplug events and
guest migration. For cases where a hotplug event is migrated, or
the guest is in the process of fetching device tree at the time of
migration, we need to ensure the device tree is created and
associated with the corresponding DRC for devices that were
hotplugged on the source, but 'coldplugged' on the target.
Signed-off-by: Jianjun Duan <duanj@linux.vnet.ibm.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
| hw/ppc/spapr.c | diffblobblamehistory | |
| hw/ppc/spapr_pci.c | diffblobblamehistory |