summaryrefslogtreecommitdiffstats
path: root/security
diff options
context:
space:
mode:
authorGavin Shan <shangw@linux.vnet.ibm.com>2012-02-27 20:04:04 +0000
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2012-03-09 11:39:29 +1100
commiteb740b5f3e6559a8f1c22e2505914d07f9632881 (patch)
tree6e463d4ba852359d82b33a61040e240430280fa6 /security
parentdef9d83da4f8587dbad5ea57c57d91e53a51006a (diff)
downloadop-kernel-dev-eb740b5f3e6559a8f1c22e2505914d07f9632881.zip
op-kernel-dev-eb740b5f3e6559a8f1c22e2505914d07f9632881.tar.gz
powerpc/eeh: Introduce EEH device
Original EEH implementation depends on struct pci_dn heavily. However, EEH shouldn't depend on that actually because EEH needn't share much information with other PCI components. That's to say, EEH should have worked independently. The patch introduces struct eeh_dev so that EEH core components needn't be working based on struct pci_dn in future. Also, struct pci_dn, struct eeh_dev instances are created in dynamic fasion and the binding with EEH device, OF node, PCI device is implemented as well. The EEH devices are created after PHBs are detected and initialized, but PCI emunation hasn't started yet. Apart from that, PHB might be created dynamically through DLPAR component and the EEH devices should be creatd as well. Another case might be OF node is created dynamically by DR (Dynamic Reconfiguration), which has been defined by PAPR. For those OF nodes created by DR, EEH devices should be also created accordingly. The binding between EEH device and OF node is done while the EEH device is initially created. The binding between EEH device and PCI device should be done after PCI emunation is done. Besides, PCI hotplug also needs the binding so that the EEH devices could be traced from the newly coming PCI buses or PCI devices. Signed-off-by: Gavin Shan <shangw@linux.vnet.ibm.com> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud