From: Bjorn Helgaas <helgaas@kernel.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-pci@vger.kernel.org, allen.m.kay@intel.com,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] pci: Wait for up to an additional 1000ms after FLR reset
Date: Tue, 16 Feb 2016 10:53:33 -0600 [thread overview]
Message-ID: <20160216165333.GB18685@localhost> (raw)
In-Reply-To: <20160212235013.16862.53910.stgit@gimli.home>
Hi Alex,
On Fri, Feb 12, 2016 at 04:51:08PM -0700, Alex Williamson wrote:
> Some devices take longer than the spec indicates to return from FLR
> reset, a notable case of this is Intel integrated graphics (IGD),
> which can often take an additional 300ms powering down an attached
> LCD panel as part of the FLR. Allow devices up to an additional
> 1000ms, testing every 100ms whether the first dword of config space
> is read as -1.
This gives me a little more heartburn about ignoring presence detect
during reset and pretending that the post-reset device is the same as
the pre-reset device. I suspect this problem wouldn't occur if we
just watched for a new device to show up after the FLR, because we
wouldn't have a timeout at all.
But given that this *is* the way we do it, ...
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
>
> Copying KVM list as this patch is required for IGD assignment.
>
> drivers/pci/pci.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index 602eb42..3b90a42 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -3414,6 +3414,25 @@ int pci_wait_for_pending_transaction(struct pci_dev *dev)
> }
> EXPORT_SYMBOL(pci_wait_for_pending_transaction);
>
> +static void pci_wait_alive(struct pci_dev *dev)
> +{
> + int i;
> + u32 id;
> +
> + for (i = 0; i < 10; i++) {
> + pci_read_config_dword(dev, PCI_VENDOR_ID, &id);
> + if (~id != 0) {
> + if (i > 0)
> + dev_info(&dev->dev, "Required additional %d"
> + "ms to return from reset\n", i * 100);
> + return;
> + }
> + msleep(100);
> + }
> +
> + dev_warn(&dev->dev, "Failed to return from reset\n");
> +}
> +
> static int pcie_flr(struct pci_dev *dev, int probe)
> {
> u32 cap;
> @@ -3430,6 +3449,7 @@ static int pcie_flr(struct pci_dev *dev, int probe)
>
> pcie_capability_set_word(dev, PCI_EXP_DEVCTL, PCI_EXP_DEVCTL_BCR_FLR);
> msleep(100);
> + pci_wait_alive(dev);
Can we fold the msleep() into pci_wait_alive(), so all the delay
happens in one place? Maybe you can add a comment to the effect that
the spec says devices should be ready 100ms after FLR, but some
devices take longer.
> return 0;
> }
>
> @@ -3460,6 +3480,7 @@ static int pci_af_flr(struct pci_dev *dev, int probe)
>
> pci_write_config_byte(dev, pos + PCI_AF_CTRL, PCI_AF_CTRL_FLR);
> msleep(100);
> + pci_wait_alive(dev);
> return 0;
> }
>
>
prev parent reply other threads:[~2016-02-16 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 23:51 [PATCH] pci: Wait for up to an additional 1000ms after FLR reset Alex Williamson
2016-02-16 16:53 ` Bjorn Helgaas [this message]
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=20160216165333.GB18685@localhost \
--to=helgaas@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=allen.m.kay@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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).