Re: [PATCH 14/14] powerpc/eeh: Move PE tree setup into the platform

2020-07-14 Thread Alexey Kardashevskiy
On 14/07/2020 13:08, Oliver O'Halloran wrote: > On Tue, Jul 14, 2020 at 11:50 AM Alexey Kardashevskiy wrote: >> >> On 06/07/2020 11:36, Oliver O'Halloran wrote: >>> /** >>> * eeh_pe_tree_insert - Add EEH device to parent PE >>> * @edev: EEH device >>> + * @new_pe_parent: PE to create addit

Re: [PATCH 14/14] powerpc/eeh: Move PE tree setup into the platform

2020-07-13 Thread Oliver O'Halloran
On Tue, Jul 14, 2020 at 11:50 AM Alexey Kardashevskiy wrote: > > On 06/07/2020 11:36, Oliver O'Halloran wrote: > > /** > > * eeh_pe_tree_insert - Add EEH device to parent PE > > * @edev: EEH device > > + * @new_pe_parent: PE to create additional PEs under > > * > > - * Add EEH device to the

Re: [PATCH 14/14] powerpc/eeh: Move PE tree setup into the platform

2020-07-13 Thread Alexey Kardashevskiy
On 06/07/2020 11:36, Oliver O'Halloran wrote: > The EEH core has a concept of a "PE tree" to support PowerNV. The PE tree > follows the PCI bus structures because a reset asserted on an upstream > bridge will be propagated to the downstream bridges. On pseries there's a > 1-1 correspondence betw

[PATCH 14/14] powerpc/eeh: Move PE tree setup into the platform

2020-07-05 Thread Oliver O'Halloran
The EEH core has a concept of a "PE tree" to support PowerNV. The PE tree follows the PCI bus structures because a reset asserted on an upstream bridge will be propagated to the downstream bridges. On pseries there's a 1-1 correspondence between what the guest sees are a PHB and a PE so the "tree"