From: Lukas Wunner <lukas@wunner.de>
To: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Yazen Ghannam <yazen.ghannam@amd.com>
Subject: Re: [PATCH v4 1/3] PCI: pciehp: Add support for async hotplug with native AER and DPC/EDR
Date: Mon, 28 Aug 2023 09:35:42 +0200 [thread overview]
Message-ID: <20230828073542.GA12658@wunner.de> (raw)
In-Reply-To: <20230815212043.114913-2-Smita.KoralahalliChannabasappa@amd.com>
On Tue, Aug 15, 2023 at 09:20:41PM +0000, Smita Koralahalli wrote:
> According to PCIe r6.0 sec 6.7.6 [1], async removal with DPC may result in
> surprise down error. This error is expected and is just a side-effect of
> async remove.
>
> Add support to handle the surprise down error generated as a side-effect
> of async remove. Typically, this error is benign as the pciehp handler
> invoked by PDC or/and DLLSC alongside DPC, de-enumerates and brings down
> the device appropriately. But the error messages might confuse users. Get
> rid of these irritating log messages with a 1s delay while pciehp waits
> for dpc recovery.
[...]
> Signed-off-by: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>
Reviewed-by: Lukas Wunner <lukas@wunner.de>
The subject is slightly inaccurate as this doesn't touch pciehp source
files, although it is *related* to pciehp.
As an example, a perhaps more accurate subject might be something like...
PCI/DPC: Ignore Surprise Down errors on hot removal
...but I don't think it's necessary to respin just for that as Bjorn is
probably able to adjust the subject to his liking when applying the patch.
Thanks a lot for patiently pursuing this issue, good to see it fixed.
Five years ago there was an attempt to solve it through masking Surprise
Down errors, which you've verified to not be a viable approach:
https://patchwork.kernel.org/project/linux-pci/patch/20180818065126.77912-2-okaya@kernel.org/
Lukas
next prev parent reply other threads:[~2023-08-28 7:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 21:20 [PATCH v4 0/3] PCI: pciehp: Add support for native AER and DPC handling on async remove Smita Koralahalli
2023-08-15 21:20 ` [PATCH v4 1/3] PCI: pciehp: Add support for async hotplug with native AER and DPC/EDR Smita Koralahalli
2023-08-28 7:35 ` Lukas Wunner [this message]
2023-09-12 22:45 ` Smita Koralahalli
2023-09-13 4:07 ` Lukas Wunner
2023-08-15 21:20 ` [PATCH v4 2/3] PCI: Enable support for 10-bit Tag during device enumeration Smita Koralahalli
2023-08-28 9:54 ` Lukas Wunner
2023-09-12 22:39 ` Smita Koralahalli
2023-08-15 21:20 ` [PATCH v4 3/3] PCI: pciehp: Clear AtomicOps unconditionally on hot remove Smita Koralahalli
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=20230828073542.GA12658@wunner.de \
--to=lukas@wunner.de \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mahesh@linux.ibm.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=yazen.ghannam@amd.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).