| commit | af8ad96bd0119ec8ac3300372fa07349e60d2178 | |
| author | David Gibson <david@gibson.dropbear.id.au> | |
| Tue, 6 Jun 2017 12:50:14 +0000 (6 22:50 +1000) | ||
| committer | David Gibson <david@gibson.dropbear.id.au> | |
| Fri, 30 Jun 2017 04:03:32 +0000 (30 14:03 +1000) | ||
| tree | b1084758b5b62f74bfc8b58db9a28eb55ea0634f | treesnapshot (tar.gz zip) |
| parent | ddd5140b1a0ffca777bb6e845912bc0d700f1f80 | commitdiff |
spapr: Start hotplugged PCI devices in ISOLATED state
PCI DRCs, and only PCI DRCs, are immediately moved to UNISOLATED isolation
state once the device is attached. This has been there from the initial
implementation, and it's not clear why.
The state diagram in PAPR 13.4 suggests PCI devices should start in
ISOLATED state until the guest moves them into UNISOLATED, and the code in
the guest-side drmgr tool seems to work that way too.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Reviewed-by: Greg Kurz <groug@kaod.org>
PCI DRCs, and only PCI DRCs, are immediately moved to UNISOLATED isolation
state once the device is attached. This has been there from the initial
implementation, and it's not clear why.
The state diagram in PAPR 13.4 suggests PCI devices should start in
ISOLATED state until the guest moves them into UNISOLATED, and the code in
the guest-side drmgr tool seems to work that way too.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Reviewed-by: Greg Kurz <groug@kaod.org>
| hw/ppc/spapr_drc.c | diffblobblamehistory |