On 2018-08-16 13:42, Benjamin Herrenschmidt wrote:
On Thu, 2018-08-16 at 13:37 +0530, poza@xxxxxxxxxxxxxx wrote:
>
> In fact looking at pcie_do_nonfatal_recovery() it's indeed completely
> broken. It tells the driver that the slot was reset without actually
> resetting anything... Ugh.
>
> Ben.
pcie_do_nonfatal_recovery() exhibit the same behavior with or without
the patch-series.
in short, there was no functional change brought in to
pcie_do_nonfatal_recovery()
Yes, I know, I'm just saying what it does is broken :-)
when I meant spec, i meant PCIe Spec.
At least spec distinguish fatal and non-fatal
"
Non-fatal errors are uncorrectable errors which cause a particular
transaction to be unreliable but the Link is otherwise fully functional.
Isolating Non-fatal from Fatal errors provides Requester/Receiver logic
in a device or system management software the opportunity to recover
from the error without resetting the components on the Link and
disturbing other transactions in progress.
"
Here the basic assumption is link is fully functional, hence we do not
initiate link reset. (while in case FATAL we do initiate Secondary Bus
Reset)
okay, so here is what current pcie_do_nonfatal_recovery() doe.
pcie_do_nonfatal_recovery
report_error_detected() >> calls driver callbacks
report_mmio_enabled()
report_slot_reset() >> if PCI_ERS_RESULT_NEED_RESET
report_resume()
If you suggest how it is broken, it will help me to understand.
probably you might want to point out what are the calls need to be added
or removed or differently handled, specially storage point of view.
Regards,
Oza.
Keep in mind that those callbacks were designed originally for EEH
(which predates AER), and so was the spec written.
We don't actually use the AER code on POWER today, so we didn't notice
how broken the implementation was :-)
We should fix that.
Either we can sort all that out by email, or we should plan some kind
of catch-up, either at Plumbers (provided I can go there) or maybe a
webex call.
Cheers,
Ben.
