Thread (7 messages) 7 messages, 4 authors, 2020-10-12

RE: [PATCH] PCI: layerscape: Change back to the default error response behavior

flat view

From: "Z.q. Hou" <zhiqiang.hou@nxp.com>
Date: 2020-10-12 04:33:40
Also in: linux-pci, lkml

Hi Rob and Kishon,
-----Original Message-----
From: Rob Herring <robh@kernel.org>
Sent: 2020年9月30日 23:08
To: Kishon Vijay Abraham I <redacted>
Cc: Z.q. Hou <zhiqiang.hou@nxp.com>; PCI <redacted>;
linux-kernel@vger.kernel.org; linux-arm-kernel
[off-list ref]; Lorenzo Pieralisi
[off-list ref]; Bjorn Helgaas [off-list ref]; M.h.
Lian [off-list ref]; Roy Zang [off-list ref]; Mingkai
Hu [off-list ref]; Leo Li [off-list ref]
Subject: Re: [PATCH] PCI: layerscape: Change back to the default error
response behavior

On Wed, Sep 30, 2020 at 8:29 AM Kishon Vijay Abraham I [off-list ref]
wrote:
quoted
Hi Hou,

On 29/09/20 6:43 pm, Zhiqiang Hou wrote:
quoted
From: Hou Zhiqiang <Zhiqiang.Hou@nxp.com>

In the current error response behavior, it will send a SLVERR
response to device's internal AXI slave system interface when the
PCIe controller experiences an erroneous completion (UR, CA and CT)
from an external completer for its outbound non-posted request,
which will result in SError and crash the kernel directly.
This patch change back it to the default behavior to increase the
robustness of the kernel. In the default behavior, it always sends
an OKAY response to the internal AXI slave interface when the
controller gets these erroneous completions. And the AER driver will
report and try to recover these errors.
I don't think not forwarding any error interrupts is a good idea.
Interrupts would be fine. Abort/SError is not. I think it is pretty clear what the
correct behavior is for config accesses.
I agree with Rob.
quoted
Maybe
you could disable it while reading configuration space registers
(vendorID and deviceID) and then enable error forwarding back?
To add to the locking (or lack of) problems in config accesses?
If take this approach, during the hole of CFG access, the error of MEM_rd will also not be forwarded, so it's not a reliable mechanism for user.

Thanks,
Zhiqiang
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help