Re: [PATCH] pcie: Add quirk for the Arm Neoverse N1SDP platform

[Robin Murphy]

On 12/12/2019 11:05 am, Andre Przywara wrote:
> On 11/12/2019 20:17, Bjorn Helgaas wrote:
>
> Hi Bjorn,
>
> > On Wed, Dec 11, 2019 at 11:00:49AM +0000, Andre Przywara wrote:
> > > On Tue, 10 Dec 2019 08:41:15 -0600
> > > Bjorn Helgaas <helgaas@xxxxxxxxxx> wrote:
> > > > On Mon, Dec 09, 2019 at 04:06:38PM +0000, Andre Przywara wrote:
> > > > > From: Deepak Pandey <Deepak.Pandey@xxxxxxx>
> > > > >
> > > > > The Arm N1SDP SoC suffers from some PCIe integration issues, most
> > > > > prominently config space accesses to not existing BDFs being answered
> > > > > with a bus abort, resulting in an SError.
> > > >
> > > > Can we tease this apart a little more?  Linux doesn't program all the
> > > > bits that control error signaling, so even on hardware that works
> > > > perfectly, much of this behavior is determined by what firmware did.
> > > > I wonder if Linux could be more careful about this.
> > > >
> > > > "Bus abort" is not a term used in PCIe.
> > >
> > > Yes, sorry, that was my sloppy term, also aiming more at the CPU
> > > side of the bus, between the cores and the RC.
> > >
> > > >   IIUC, a config read to a
> > > > device that doesn't exist should terminate with an Unsupported Request
> > > > completion, e.g., see the implementation note in PCIe r5.0 sec 2.3.1.
> > >
> > > Yes, that's what Lorenzo mentioned as well.
> > >
> > > > The UR should be an uncorrectable non-fatal error (Table 6-5), and
> > > > Figures 6-2 and 6-3 show how it should be handled and when it should
> > > > be signaled as a system error.  In case you don't have a copy of the
> > > > spec, I extracted those two figures and put them at [1].
> > >
> > > Thanks for that.
> > > So in the last few months we tossed several ideas around how to
> > > work-around this without kernel intervention, all of them turned out
> > > to be not working. There are indeed registers in the RC that
> > > influence error reporting to the CPU side, but even if we could
> > > suppress (or catch) the SError, we can't recover and fixup the read
> > > transaction to the CPU. Even Lorenzo gave up on this ;-) As far as I
> > > understood this, there are gates missing which are supposed to
> > > translate this specific UR into a valid "all-1s" response.
> >
> > But the commit log says firmware scanned the bus (catching the
> > SErrors).  Shouldn't Linux be able to catch them the same way?
>
> Not really. The scanning is done by the SCP management processor, which is a Cortex-M class core on the same bus. So it's a simple, single core running very early after power-on, when the actual AP cores are still off. The SError handler is set to just increase a value, then to return. This value is then checked before and after a config space access for a given
> BDF: https://git.linaro.org/landing-teams/working/arm/n1sdp-pcie-quirk.git/tree/scp
>
> On the AP cores that run Linux later on this is quite different: The SError is asynchronous, imprecise (inexact) and has no syndrome information. That means we can't attribute this anymore to the faulting instruction, we don't even know if it happened due to this config space access. The CPU might have executed later instructions already, so the state is broken at this point. SError basically means: the system is screwed up.
> Because this is quite common for SErrors, we don't even allow to register SError handlers in arm64 Linux.

Furthermore, on the main application processor, SError might be 
delivered to EL3 firmware well beyond the reach of Linux, so we can make 
zero assumptions about how it's handled and whether we'll ever see it, 
or survive the result (EL3 is at liberty to say "oh, something went 
wrong, I'll reset the system immediately").

Robin.
> So even if we could somehow handle this is in Linux, it would be a much greater and intrusive hack, so I'd rather stick with this version.
>   
> > The "all-1s" response directly from hardware is typical of most
> > platforms, but I don't think it's strictly required by the PCIe spec
> > and I don't think it's absolutely essential even to Linux.  If you can
> > catch the SErrors, isn't there a way for software to fabricate that
> > all-1s data and continue after the read?
>
> That was an idea we had as well, but due to the points mentioned above this is not possible.
>
> > > > Even ECAM compliance is not really minor -- if this controller were
> > > > fully compliant with the spec, you would need ZERO Linux changes to
> > > > support it.  Every quirk like this means additional maintenance
> > > > burden, and it's not just a one-time thing.  It means old kernels that
> > > > *should* "just work" on your system will not work unless somebody
> > > > backports the quirk.
> > >
> > > I am well aware of that, and we had quite some discussions
> > > internally, with quite some opposition.  ...
> >
> > The main point is that *future* silicon should be designed to avoid
> > this issue.  I hope at least that part was not controversial.
>
> Yes, the design goal was to be completely standards (SBSA, ACPI, ECAM) compliant, it was just the usual "things happen" that wasn't spotted in time.
>
> > If we want to take advantage of the generic PCI code supplied by
> > Linux, we have to expect that the hardware will play by the rules of
> > PCI.
>
> You don't need to convince me ;-), but I think the lesson has been learned.
>
> Cheers,
> Andre.
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel