[lkml]   [2017]   [Dec]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v2 2/4] PCI/DPC/AER: Address Concurrency between AER and DPC
On 2017-12-29 23:43, Keith Busch wrote:
> On Fri, Dec 29, 2017 at 11:30:02PM +0530, wrote:
>> On 2017-12-29 22:53, Keith Busch wrote:
>> > 2. A DPC event suppresses the error message required for the Linux
>> > AER driver to run. How can AER and DPC run concurrently?
>> I afraid I could not grasp the first line completely.
> A DPC capable and enabled port discards error messages; the ERR_FATAL
> or ERR_NONFATAL message required to trigger AER handling won't exist in
> such a setup.
> This behavior is defined in the specification 6.2.10 for Downstream
> Port Containment:
> When DPC is triggered due to receipt of an uncorrectable error
> Message,
> the Requester ID from the Message is recorded in the DPC Error
> Source ID register and that Message is discarded and not forwarded
> Upstream. When DPC is triggered by an unmasked uncorrectable error,
> that error will not be signaled with an uncorrectable error Message,
> even if otherwise enabled.

In my understanding, thiis talks about DPC enabled switch. this case is
taken care as well.
if you look at patchset-3, when AER is triggered, AER's pci_dev is of
will traverse all the way up until it finds associated DPC service
pdev = pcie_port_upstream_bridge(dev);

if AER is not triggered, then at switch level DPC will take
care/suppress the msg
and entire SW will not come into picture then.

But specifically the patches attempts to bring in some sort of
coordination and understanding between AER and DPC.
as I mentioned in my previous mail.


 \ /
  Last update: 2017-12-30 04:58    [W:0.038 / U:0.668 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site