From: Bjorn Helgaas <helgaas@kernel.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
linux-kernel@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH 2/2] PCI: Do not wait for disconnected devices when resuming
Date: Mon, 29 Jan 2024 12:55:44 -0600 [thread overview]
Message-ID: <20240129185544.GA471021@bhelgaas> (raw)
In-Reply-To: <20240129112710.2852-3-ilpo.jarvinen@linux.intel.com>
On Mon, Jan 29, 2024 at 01:27:10PM +0200, Ilpo Järvinen wrote:
> On runtime resume, pci_dev_wait() is called:
> pci_pm_runtime_resume()
> pci_pm_bridge_power_up_actions()
> pci_bridge_wait_for_secondary_bus()
> pci_dev_wait()
>
> While a device is runtime suspended along with its PCIe hierarchy, the
> device could get disconnected. In such case, the link will not come up
> no matter how log pci_dev_wait() waits for it.
s/PCIe/PCI/ (unless this is a PCIe-specific thing)
s/log/long/
> Besides the above mentioned case, there could be other ways to get the
> device disconnected while pci_dev_wait() is waiting for the link to
> come up.
>
> Make pci_dev_wait() to exit if the device is already disconnected to
> avoid unnecessary delay. As disconnected device is not really even a
> failure in the same sense as link failing to come up for whatever
> reason, return 0 instead of errno.
The device being disconnected is not the same as a link failure. Do
all the callers do the right thing if pci_dev_wait() returns success
when there's no device there?
> Also make sure compiler does not become too clever with
> dev->error_state and use READ_ONCE() to force a fetch for the
> up-to-date value.
I think we should have a comment there to say why READ_ONCE() is
needed. Otherwise it's hard to know whether a future change might
make it unnecessary.
> Reported-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> ---
> drivers/pci/pci.c | 5 +++++
> drivers/pci/pci.h | 4 +++-
> 2 files changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index d8f11a078924..ec9bf6c90312 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -1250,6 +1250,11 @@ static int pci_dev_wait(struct pci_dev *dev, char *reset_type, int timeout)
> for (;;) {
> u32 id;
>
> + if (pci_dev_is_disconnected(dev)) {
> + pci_dbg(dev, "disconnected; not waiting\n");
> + return 0;
> + }
> +
> pci_read_config_dword(dev, PCI_COMMAND, &id);
> if (!PCI_POSSIBLE_ERROR(id))
> break;
> diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h
> index 2336a8d1edab..563a275dff67 100644
> --- a/drivers/pci/pci.h
> +++ b/drivers/pci/pci.h
> @@ -4,6 +4,8 @@
>
> #include <linux/pci.h>
>
> +#include <asm/rwonce.h>
> +
> /* Number of possible devfns: 0.0 to 1f.7 inclusive */
> #define MAX_NR_DEVFNS 256
>
> @@ -370,7 +372,7 @@ static inline int pci_dev_set_disconnected(struct pci_dev *dev, void *unused)
>
> static inline bool pci_dev_is_disconnected(const struct pci_dev *dev)
> {
> - return dev->error_state == pci_channel_io_perm_failure;
> + return READ_ONCE(dev->error_state) == pci_channel_io_perm_failure;
> }
>
> /* pci_dev priv_flags */
> --
> 2.39.2
>
next prev parent reply other threads:[~2024-01-29 18:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 11:27 [PATCH 0/2] PCI: Fix disconnect related issues Ilpo Järvinen
2024-01-29 11:27 ` [PATCH 1/2] PCI: Clear LBMS on resume to avoid Target Speed quirk Ilpo Järvinen
2024-01-29 18:43 ` Bjorn Helgaas
2024-01-30 11:53 ` Ilpo Järvinen
2024-01-30 16:41 ` Maciej W. Rozycki
2024-01-30 17:33 ` Ilpo Järvinen
2024-02-01 9:47 ` Ilpo Järvinen
2024-02-01 18:49 ` Maciej W. Rozycki
2024-02-02 15:27 ` Ilpo Järvinen
2024-02-07 12:33 ` Ilpo Järvinen
2024-08-09 13:25 ` Maciej W. Rozycki
2024-08-09 15:55 ` Ilpo Järvinen
2024-08-12 11:59 ` Maciej W. Rozycki
2024-02-12 17:56 ` Maciej W. Rozycki
2024-01-29 11:27 ` [PATCH 2/2] PCI: Do not wait for disconnected devices when resuming Ilpo Järvinen
2024-01-29 18:55 ` Bjorn Helgaas [this message]
2024-01-30 13:15 ` Ilpo Järvinen
2024-02-02 17:03 ` Ilpo Järvinen
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=20240129185544.GA471021@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=mika.westerberg@linux.intel.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