> Prarit Bhargava <prarit <at> redhat.com> writes:
>
>> /**
>> diff --git a/drivers/pci/pcie/aer/aerdrv.c b/drivers/pci/pcie/aer/aerdrv.c
>> index 58ad791..dd6b352 100644
>> --- a/drivers/pci/pcie/aer/aerdrv.c
>> +++ b/drivers/pci/pcie/aer/aerdrv.c
>> @@ -346,6 +346,9 @@ static pci_ers_result_t aer_root_reset(struct pci_dev *dev)
>> u32 reg32;
>> int pos;
>>
>> + if (dev->rp_AER_panic)
>> + panic("%s: AER detected on Root Port", pci_name(dev));
>> +
>> pos = pci_find_ext_capability(dev, PCI_EXT_CAP_ID_ERR);
>>
>
>
> I really like this idea. I just wonder if the panic can happen in do_recovery in
> aerdrv_core.c before the broadcast_error_message() is done that invokes all of
> the error_detected callbacks. It would be best to panic as soon as possible to
> increase error containment.
Hi Betty,
Thanks for the review.
IMO that sounds like a better idea. As you said, panicking early as possible in
order to increase error containment is the best option.
Bjorn, any objection to moving the panic up as far as possible?
I'll let the rest of the discussion settle before putting out a [v3].
P.
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
