From: Yury Murashka <yurypm@arista.com>
To: bhelgaas@google.com
Cc: lukas@wunner.de, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, Yury Murashka <yurypm@arista.com>,
James Sewart <jamessewart@arista.com>
Subject: [PATCH v2] PCI: Stop waiting for link status after config read failure
Date: Mon, 7 Sep 2026 12:38:53 +0000 [thread overview]
Message-ID: <20260907123853.1081635-1-yurypm@arista.com> (raw)
In-Reply-To: <20260904111318.1063858-1-yurypm@arista.com>
With a nested PCIe topology with multiple layers of hotplug, a link can go
down near the bottom of the topology shortly before a link above it goes
down. In that case, pcie_wait_for_link_status() can wait for the full
timeout while every read of the link status register fails because the
device has disappeared.
Return immediately when the device is disconnected so event processing can
continue.
Signed-off-by: Yury Murashka <yurypm@arista.com>
Co-authored-by: James Sewart <jamessewart@arista.com>
---
drivers/pci/pci.c | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
Changes in v2:
- Check pci_dev_is_disconnected() before reading link status instead of
checking the return value of pcie_capability_read_word().
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index b2879a6be..a568d5ac1 100644
--- a/drivers/pci/pci.c
+++ b/drivers/pci/pci.c
@@ -4565,8 +4565,9 @@ static int pci_pm_reset(struct pci_dev *dev, bool probe)
* @use_lt: Use the LT bit if TRUE, or the DLLLA bit if FALSE.
* @active: Waiting for active or inactive?
*
- * Return 0 if successful, or -ETIMEDOUT if status has not changed within
- * PCIE_LINK_RETRAIN_TIMEOUT_MS milliseconds.
+ * Return 0 if successful, -ENODEV if the device is disconnected, or
+ * -ETIMEDOUT if status has not changed within PCIE_LINK_RETRAIN_TIMEOUT_MS
+ * milliseconds.
*/
static int pcie_wait_for_link_status(struct pci_dev *pdev,
bool use_lt, bool active)
@@ -4580,6 +4581,8 @@ static int pcie_wait_for_link_status(struct pci_dev *pdev,
end_jiffies = jiffies + msecs_to_jiffies(PCIE_LINK_RETRAIN_TIMEOUT_MS);
do {
+ if (pci_dev_is_disconnected(pdev))
+ return -ENODEV;
pcie_capability_read_word(pdev, PCI_EXP_LNKSTA, &lnksta);
if ((lnksta & lnksta_mask) == lnksta_match)
return 0;
@@ -4603,8 +4605,9 @@ static int pcie_wait_for_link_status(struct pci_dev *pdev,
* according to @use_lt. It is not verified whether the use of the DLLLA
* bit is valid.
*
- * Return 0 if successful, or -ETIMEDOUT if training has not completed
- * within PCIE_LINK_RETRAIN_TIMEOUT_MS milliseconds.
+ * Return 0 if successful, -ENODEV if the device is disconnected, or
+ * -ETIMEDOUT if training has not completed within PCIE_LINK_RETRAIN_TIMEOUT_MS
+ * milliseconds.
*/
int pcie_retrain_link(struct pci_dev *pdev, bool use_lt)
{
base-commit: a500db7819c50db59e55f1b4fa1c3baa5a2616f3
--
2.51.0
next prev parent reply other threads:[~2026-09-07 12:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 11:13 [PATCH] PCI: Stop waiting for link status after config read failure Yury Murashka
2026-09-04 11:28 ` sashiko-bot
2026-09-04 11:59 ` Ilpo Järvinen
2026-09-04 12:20 ` Lukas Wunner
2026-09-04 15:36 ` Yury M.
2026-09-04 20:20 ` Ilpo Järvinen
2026-09-05 10:06 ` Lukas Wunner
2026-09-09 13:15 ` Yury M.
2026-09-07 12:38 ` Yury Murashka [this message]
2026-09-07 12:53 ` [PATCH v2] " sashiko-bot
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=20260907123853.1081635-1-yurypm@arista.com \
--to=yurypm@arista.com \
--cc=bhelgaas@google.com \
--cc=jamessewart@arista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
/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