On Friday 07 January 2022 14:34:15 Bjorn Helgaas wrote: > On Fri, Jan 07, 2022 at 11:04:58AM +0100, Pali Rohár wrote: > > Hello! You asked me in another email for comments to this email, so I'm > > replying directly to this email... > > > > On Tuesday 04 January 2022 10:02:18 Stefan Roese wrote: > > > Hi, > > > > > > I'm trying to get the Kernel PCIe AER infrastructure to work on my > > > ZynqMP based system. E.g. handle the events (correctable, uncorrectable > > > etc). In my current tests, no AER interrupt is generated though. I'm > > > currently using the "surprise down error status" in the uncorrectable > > > error status register of the connected PCIe switch (PLX / Broadcom > > > PEX8718). Here the bit is correctly logged in the PEX switch > > > uncorrectable error status register but no interrupt is generated > > > to the root-port / system. And hence no AER message(s) reported. > > I think the error should also be logged in the Root Port AER > Capability. And of course the interrupt enable bits in the Root Error > Command register would have to be set. > > > > Does any one of you have some ideas on what might be missing? Why are > > > these events not reported to the PCIe rootport driver via IRQ? Might > > > this be a problem of the missing MSI-X support of the ZynqMP? The AER > > > interrupt is connected as legacy IRQ: > > > > > > cat /proc/interrupts | grep -i aer > > > 58: 0 0 0 0 nwl_pcie:legacy 0 Level > > > PCIe PME, aerdrv > > I guess this means whatever INTx the Root Port is using is connected > to IRQ 58? Can you tell whether that INTx works if a device below the > Root Port uses it? Or whether it is asserted for PMEs? > > > Error events (correctable, non-fatal and fatal) are reported by PCIe > > devices to the Root Complex via PCIe error messages (Message code of TLP > > is set to Error Message) and not via interrupts. Root Port is then > > responsible to "convert" these PCIe error messages to MSI(X) interrupt > > and report it to the system. According to PCIe spec, AER is supported > > only via MSI(X) interrupts, not legacy INTx. > > Where does it say that? PCIe r5.0, sec 6.2.4.1.2 and 6.2.6, both > mention INTx, and the diagram in 6.2.6 even shows possible > platform-specific System Error signaling. Kernel AER driver is not available when MSI is not supported: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pci/pcie/aer.c?h=v5.15#n112 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pci/pcie/portdrv_core.c?h=v5.15#n224 Originally this was my primary indication that AER is MSI(X)-only. And my understanding is that AER Root Error Status Register (7.8.4.10) specifies Advanced Error Interrupt Message Number which indicates which MSI(X) interrupt is used. And there is no information about INTx if you enable particular reporting category via AER Root Error Command Register. That is why I was in impression that AER interrupts are MSI-only. But now I'm looking at 6.2.4.1.2 section and seems that AER can really use INTx. So I was wrong here. But why then kernel AER driver has check that AER is available only when MSI is enabled? And not available when MSI is disabled? > But I doubt Linux is smart enough to configure this correctly for > INTx. You could experiment by setting the AER control bits with > setpci. > > There was some previous discussion, and it even mentions ZynqMP as a > device that has a dedicated non-MSI mechanism for AER signaling: > > https://lore.kernel.org/linux-pci/1533141889-19962-1-git-send-email-bharat.kumar.gogada@xxxxxxxxxx/ > https://lore.kernel.org/all/1464242406-20203-1-git-send-email-po.liu@xxxxxxx/T/#u > > But I don't think it went anywhere. > > It seems like maybe this *could* be made to work. > > Bjorn So, seems that this is anther PCIe controller which does not report AER interrupt via standard MSI interrupts but via some vendor-specific way.
