From: poza@codeaurora.org
To: Sinan Kaya <okaya@kernel.org>
Cc: Lukas Wunner <lukas@wunner.de>,
linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Keith Busch <keith.busch@intel.com>,
linux-pci-owner@vger.kernel.org
Subject: Re: [PATCH v7 1/1] PCI: pciehp: Ignore link events when there is a fatal error pending
Date: Mon, 06 Aug 2018 20:42:30 +0530 [thread overview]
Message-ID: <16b40dfd99c37c67e3d103f6fb7738ef@codeaurora.org> (raw)
In-Reply-To: <22ce7172-b028-c0b1-d117-8096e016b15b@kernel.org>
On 2018-08-06 20:36, Sinan Kaya wrote:
> On 8/6/2018 11:04 AM, Sinan Kaya wrote:
>>> Either AER or DPC would get triggered, not both.
>>> in that case, if AER is disabled, then this code will return false
>>> thinking HP needs to handle it.
>>> but it might be that DPC would be triggering as well.
>>> but I dont see DPC check anywhere, rather we are relying on
>>> PCI_EXP_DEVSTA
>>> and following condition:
>>> if (!pdev->aer_cap)
>>> return false;
>>> so here we dont check anything with respect to DPC capability
>>> (although there is no such thing as dpc_cap)
>>> (except If I missed something)
>>
>> That's true. We either need to go poll every single source (AER/DPC)
>> for
>> an error or rely on the DEVSTA. For ease of implementation, I suggest
>> DEVSTA. Something like this:
>
> Hmm. Too quick...
>
> Reduced set doesn't help. Surprise Link Down is also a fatal error.
> That's what I was trying to exclude. We'll have to poll the error
> source.
How about using pcie_port_find_service() ?
Regards,
Oza.
next prev parent reply other threads:[~2018-08-06 17:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-05 22:51 [PATCH v7 0/1] PCI: Handle conflict between hotplug and error handling Sinan Kaya
2018-08-05 22:51 ` [PATCH v7 1/1] PCI: pciehp: Ignore link events when there is a fatal error pending Sinan Kaya
2018-08-06 7:51 ` poza
2018-08-06 9:26 ` Lukas Wunner
2018-08-06 14:55 ` poza
2018-08-06 15:04 ` Sinan Kaya
2018-08-06 15:06 ` Sinan Kaya
2018-08-06 15:12 ` poza [this message]
2018-08-06 16:34 ` Sinan Kaya
2018-08-06 16:44 ` Lukas Wunner
2018-08-06 16:49 ` Sinan Kaya
2018-08-06 17:03 ` Sinan Kaya
2018-08-06 17:05 ` Lukas Wunner
2018-08-06 17:09 ` Sinan Kaya
2018-08-06 9:30 ` Lukas Wunner
2018-09-04 18:18 ` [PATCH v7 0/1] PCI: Handle conflict between hotplug and error handling Bjorn Helgaas
2018-09-04 18:28 ` Sinan Kaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16b40dfd99c37c67e3d103f6fb7738ef@codeaurora.org \
--to=poza@codeaurora.org \
--cc=bhelgaas@google.com \
--cc=keith.busch@intel.com \
--cc=linux-pci-owner@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mika.westerberg@linux.intel.com \
--cc=okaya@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.