From: David Woodhouse <dwmw2@infradead.org>
To: Stanislav Spassov <stanspas@amazon.com>, linux-pci@vger.kernel.org
Cc: "Stanislav Spassov" <stanspas@amazon.de>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Jan H . Schönherr" <jschoenh@amazon.de>,
"Jonathan Corbet" <corbet@lwn.net>,
"Ashok Raj" <ashok.raj@intel.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Sinan Kaya" <okaya@kernel.org>,
"Rajat Jain" <rajatja@google.com>
Subject: Re: [PATCH v4 0/3] Improve PCI device post-reset readiness polling
Date: Fri, 22 Jan 2021 08:54:12 +0000 [thread overview]
Message-ID: <8c9c45025b6130719d23c2fe151e2b6d3eef3baf.camel@infradead.org> (raw)
In-Reply-To: <20200307172044.29645-1-stanspas@amazon.com>
[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]
On Sat, 2020-03-07 at 18:20 +0100, Stanislav Spassov wrote:
> From: Stanislav Spassov <stanspas@amazon.de>
>
> The first version of this patch series can be found here:
> https://lore.kernel.org/linux-pci/20200223122057.6504-1-stanspas@amazon.com
>
> The goal of this patch series is to solve an issue where pci_dev_wait
> can cause system crashes. After a reset, a hung device may keep
> responding with CRS completions indefinitely. If CRS Software Visibility
> is enabled on the Root Port, attempting to read any register other than
> PCI_VENDOR_ID will cause the Root Port to autonomously retry the request
> without reporting back to the CPU core. Unless the number of retries or
> the amount of time spent retrying is limited by platform-specific means,
> this scenario leads to low-level platform timeouts (such as a TOR
> Timeout), which can easily escalate to a crash.
>
> Feedback on the v1 inspired a lot of additional improvements all around the
> device reset codepaths and reducing post-reset delays. These improvements
> were published as part of v2 (v3 is just small build fixes).
>
> It looks like there is immediate demand specifically for the CRS work,
> so I am once again reducing the series to just that. The reset will be
> posted as a separate patch series that will likely require more time and
> iterations to stabilize.
Hm, what happened to this?
Bjorn?
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2021-01-22 8:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 17:20 [PATCH v4 0/3] Improve PCI device post-reset readiness polling Stanislav Spassov
2020-03-07 17:20 ` [PATCH v4 1/3] PCI: Refactor polling loop out of pci_dev_wait Stanislav Spassov
2020-03-07 17:20 ` [PATCH v4 2/3] PCI: Cache CRS Software Visibiliy in struct pci_dev Stanislav Spassov
2021-09-12 13:32 ` Bjorn Helgaas
2021-09-13 16:06 ` Spassov, Stanislav
2020-03-07 17:20 ` [PATCH v4 3/3] PCI: Add CRS handling to pci_dev_wait() Stanislav Spassov
2020-03-09 15:55 ` Sinan Kaya
2020-03-09 16:19 ` Raj, Ashok
2020-03-09 16:38 ` Spassov, Stanislav
2020-03-09 17:33 ` Sinan Kaya
2021-09-11 14:03 ` Bjorn Helgaas
2021-09-13 16:29 ` Spassov, Stanislav
2021-09-13 16:38 ` Bjorn Helgaas
2021-09-13 18:04 ` Spassov, Stanislav
2021-09-14 17:53 ` Rajat Jain
2021-09-13 16:07 ` Bjorn Helgaas
2021-09-13 16:39 ` Spassov, Stanislav
2021-01-22 8:54 ` David Woodhouse [this message]
2021-09-10 9:32 ` [PATCH v4 0/3] Improve PCI device post-reset readiness polling David Woodhouse
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=8c9c45025b6130719d23c2fe151e2b6d3eef3baf.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=ashok.raj@intel.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=jschoenh@amazon.de \
--cc=linux-pci@vger.kernel.org \
--cc=okaya@kernel.org \
--cc=rajatja@google.com \
--cc=stanspas@amazon.com \
--cc=stanspas@amazon.de \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).