From: Lukas Wunner <lukas@wunner.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Jiwei <jiwei.sun.bj@qq.com>,
macro@orcam.me.uk, bhelgaas@google.com,
linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
guojinhui.liam@bytedance.com, helgaas@kernel.org,
ahuang12@lenovo.com, sunjw10@lenovo.com
Subject: Re: [PATCH 2/2] PCI: Fix the PCIe bridge decreasing to Gen 1 during hotplug testing
Date: Wed, 15 Jan 2025 11:18:47 +0100 [thread overview]
Message-ID: <Z4eLh24IkDrAm6cm@wunner.de> (raw)
In-Reply-To: <3d7c3904-a52e-9602-3ad2-29b5981729c7@linux.intel.com>
On Tue, Jan 14, 2025 at 08:25:04PM +0200, Ilpo Järvinen wrote:
> On Tue, 14 Jan 2025, Jiwei wrote:
> > [ 539.362400] ==== pcie_bwnotif_irq 269(stop running),link_status:0x7841
> > [ 539.395720] ==== pcie_bwnotif_irq 247(start running),link_status:0x1041
>
> DLLLA=0
>
> But LBMS did not get reset.
>
> So is this perhaps because hotplug cannot keep up with the rapid
> remove/add going on, and thus will not always call the remove_board()
> even if the device went away?
>
> Lukas, do you know if there's a good way to resolve this within hotplug
> side?
I believe the pciehp code is fine and suspect this is an issue
in the quirk. We've been dealing with rapid add/remove in pciehp
for years without issues.
I don't understand the quirk sufficiently to make a guess
what's going wrong, but I'm wondering if there could be
a race accessing the lbms_count?
Maybe if lbms_count is replaced by a flag in pci_dev->priv_flags
as we've discussed, with proper memory barriers where necessary,
this problem will solve itself?
Thanks,
Lukas
next prev parent reply other threads:[~2025-01-15 10:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 13:44 [PATCH 2/2] PCI: Fix the PCIe bridge decreasing to Gen 1 during hotplug testing Jiwei Sun
2025-01-11 16:00 ` Maciej W. Rozycki
2025-01-13 12:44 ` Jiwei
2025-01-13 15:08 ` Ilpo Järvinen
2025-01-14 15:04 ` Jiwei
2025-01-14 18:25 ` Ilpo Järvinen
2025-01-15 10:18 ` Lukas Wunner [this message]
2025-11-25 19:23 ` [External] : " ALOK TIWARI
2025-12-01 3:54 ` Maciej W. Rozycki
2025-01-15 11:39 ` Jiwei
2025-09-09 12:33 ` [External] : " ALOK TIWARI
-- strict thread matches above, loose matches on Subject: below --
2025-12-01 3:52 [PATCH] PCI: Always lift 2.5GT/s restriction in PCIe failed link retraining Maciej W. Rozycki
2025-12-04 1:40 ` [PATCH 2/2] PCI: Fix the PCIe bridge decreasing to Gen 1 during hotplug testing Matthew W Carlis
2025-12-04 23:43 ` Maciej W. Rozycki
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=Z4eLh24IkDrAm6cm@wunner.de \
--to=lukas@wunner.de \
--cc=ahuang12@lenovo.com \
--cc=bhelgaas@google.com \
--cc=guojinhui.liam@bytedance.com \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jiwei.sun.bj@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=sunjw10@lenovo.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