Re: powerpc/powernv: Don't warn on PE init if unfreeze is unsupported

On Wed, 2016-11-16 at 01:12:26 UTC, Russell Currey wrote: > Whenever a PE is initialised in powernv, opal_pci_eeh_freeze_clear() is > called. This is to remove any existing freeze, and has no negative side > effects if the PE is already in an unfrozen state. On PHB backends that > don't support t

Re: [PATCH] powerpc/powernv: Don't warn on PE init if unfreeze is unsupported

On 16/11/16 12:12, Russell Currey wrote: Whenever a PE is initialised in powernv, opal_pci_eeh_freeze_clear() is called. This is to remove any existing freeze, and has no negative side effects if the PE is already in an unfrozen state. On PHB backends that don't support this operation and retur

Re: [PATCH] powerpc/powernv: Don't warn on PE init if unfreeze is unsupported

On Wed, Nov 16, 2016 at 12:12:26PM +1100, Russell Currey wrote: >Whenever a PE is initialised in powernv, opal_pci_eeh_freeze_clear() is >called. This is to remove any existing freeze, and has no negative side >effects if the PE is already in an unfrozen state. On PHB backends that >don't support

[PATCH] powerpc/powernv: Don't warn on PE init if unfreeze is unsupported

Whenever a PE is initialised in powernv, opal_pci_eeh_freeze_clear() is called. This is to remove any existing freeze, and has no negative side effects if the PE is already in an unfrozen state. On PHB backends that don't support this operation and return OPAL_UNSUPPORTED, this creates a scary an