From: Keith Busch <kbusch@meta.com>
To: <bhelgaas@google.com>, <linux-pci@vger.kernel.org>
Cc: <ilpo.jarvinen@linux.intel.com>, <lukas@wunner.de>,
Keith Busch <kbusch@kernel.org>
Subject: [PATCHv2] pci: allow user specifiy a reset poll timeout
Date: Tue, 18 Feb 2025 08:54:44 -0800 [thread overview]
Message-ID: <20250218165444.2406119-1-kbusch@meta.com> (raw)
From: Keith Busch <kbusch@kernel.org>
The spec does not provide any upper limit to how long a device may
return Request Retry Status. It just says "Some devices require a
lengthy self-initialization sequence to complete". The kernel
arbitrarily chose 60 seconds since that really ought to be enough. But
there are devices where this turns out not to be enough.
Since any timeout choice would be arbitrary, and 60 seconds is generally
more than enough for the majority of hardware, let's make this a
parameter so an admin can adjust it specifically to their needs if the
default timeout isn't appropriate.
Signed-off-by: Keith Busch <kbusch@kernel.org>
---
v1->v2:
The user interface is in seconds granularity just to be more user
friendly. I don't think anyone needs millisecond granularity here.
This also required clamping the value to prevent any possible overflow
from bad user values.
Replaced the macro aliasing the kernel param variable to just directly
use the param variable. The variable is also renamed to match the
define that it's replacing.
.../admin-guide/kernel-parameters.txt | 3 +++
drivers/pci/pci.c | 18 ++++++++++++------
2 files changed, 15 insertions(+), 6 deletions(-)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index fb8752b42ec85..148d0f37b6594 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -4843,6 +4843,9 @@
Note: this may remove isolation between devices
and may put more devices in an IOMMU group.
+ reset_wait=nn The number of seconds to wait after a reset
+ while seeing Request Retry Status. Default is
+ 60 (1 minute).
force_floating [S390] Force usage of floating interrupts.
nomio [S390] Do not use MIO instructions.
norid [S390] ignore the RID field and force use of
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index 869d204a70a37..b0ee84b90a22e 100644
--- a/drivers/pci/pci.c
+++ b/drivers/pci/pci.c
@@ -75,7 +75,7 @@ struct pci_pme_device {
* limit, but 60 sec ought to be enough for any device to become
* responsive.
*/
-#define PCIE_RESET_READY_POLL_MS 60000 /* msec */
+static int pci_reset_ready_poll_ms = 60000;
static void pci_dev_d3_sleep(struct pci_dev *dev)
{
@@ -4549,7 +4549,7 @@ int pcie_flr(struct pci_dev *dev)
*/
msleep(100);
- return pci_dev_wait(dev, "FLR", PCIE_RESET_READY_POLL_MS);
+ return pci_dev_wait(dev, "FLR", pci_reset_ready_poll_ms);
}
EXPORT_SYMBOL_GPL(pcie_flr);
@@ -4616,7 +4616,7 @@ static int pci_af_flr(struct pci_dev *dev, bool probe)
*/
msleep(100);
- return pci_dev_wait(dev, "AF_FLR", PCIE_RESET_READY_POLL_MS);
+ return pci_dev_wait(dev, "AF_FLR", pci_reset_ready_poll_ms);
}
/**
@@ -4661,7 +4661,7 @@ static int pci_pm_reset(struct pci_dev *dev, bool probe)
pci_write_config_word(dev, dev->pm_cap + PCI_PM_CTRL, csr);
pci_dev_d3_sleep(dev);
- return pci_dev_wait(dev, "PM D3hot->D0", PCIE_RESET_READY_POLL_MS);
+ return pci_dev_wait(dev, "PM D3hot->D0", pci_reset_ready_poll_ms);
}
/**
@@ -4928,7 +4928,7 @@ int pci_bridge_wait_for_secondary_bus(struct pci_dev *dev, char *reset_type)
return -ENOTTY;
return pci_dev_wait(child, reset_type,
- PCIE_RESET_READY_POLL_MS - PCI_RESET_WAIT);
+ pci_reset_ready_poll_ms - PCI_RESET_WAIT);
}
pci_dbg(dev, "waiting %d ms for downstream link, after activation\n",
@@ -4940,7 +4940,7 @@ int pci_bridge_wait_for_secondary_bus(struct pci_dev *dev, char *reset_type)
}
return pci_dev_wait(child, reset_type,
- PCIE_RESET_READY_POLL_MS - delay);
+ pci_reset_ready_poll_ms - delay);
}
void pci_reset_secondary_bus(struct pci_dev *dev)
@@ -6841,6 +6841,12 @@ static int __init pci_setup(char *str)
disable_acs_redir_param = str + 18;
} else if (!strncmp(str, "config_acs=", 11)) {
config_acs_param = str + 11;
+ } else if (!strncmp(str, "reset_wait=", 11)) {
+ unsigned long val;
+
+ val = clamp(simple_strtoul(str + 11, &str, 0),
+ 1, INT_MAX / MSEC_PER_SEC);
+ pci_reset_ready_poll_ms = val * MSEC_PER_SEC;
} else {
pr_err("PCI: Unknown option `%s'\n", str);
}
--
2.43.5
next reply other threads:[~2025-02-18 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 16:54 Keith Busch [this message]
2025-04-15 0:11 ` [PATCHv2] pci: allow user specifiy a reset poll timeout Keith Busch
2025-06-11 16:28 ` Manivannan Sadhasivam
2025-06-11 16:40 ` Keith Busch
2025-06-11 17:11 ` Manivannan Sadhasivam
2025-06-11 17:17 ` Keith Busch
2025-06-12 8:06 ` Ilpo Järvinen
2025-06-23 17:51 ` Keith Busch
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=20250218165444.2406119-1-kbusch@meta.com \
--to=kbusch@meta.com \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kbusch@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 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.