public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Matthew W Carlis" <mattc@purestorage.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Mika Westerberg" <mika.westerberg@linux.intel.com>,
	"Oliver O'Halloran" <oohall@gmail.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] PCI: Rework error reporting with PCIe failed link retraining
Date: Fri, 9 Aug 2024 14:57:27 -0500	[thread overview]
Message-ID: <20240809195727.GA209985@bhelgaas> (raw)
In-Reply-To: <alpine.DEB.2.21.2408091017050.61955@angie.orcam.me.uk>

On Fri, Aug 09, 2024 at 02:24:40PM +0100, Maciej W. Rozycki wrote:
> Hi,
> 
>  This is v2 superseding a patch series originally posted here: 
> <https://lore.kernel.org/r/alpine.DEB.2.21.2402092125070.2376@angie.orcam.me.uk/>.
> 
>  This patch series addresses issues observed by Ilpo as reported here: 
> <https://lore.kernel.org/r/aa2d1c4e-9961-d54a-00c7-ddf8e858a9b0@linux.intel.com/>, 
> one with excessive delays happening when `pcie_failed_link_retrain' is 
> called, but link retraining has not been actually attempted, and another 
> one with an API misuse caused by a merge mistake.
> 
>  It also addresses an issue observed by Matthew as discussed here: 
> <https://lore.kernel.org/r/20240806000659.30859-1-mattc@purestorage.com/> 
> and here: 
> <https://lore.kernel.org/r/20240722193407.23255-1-mattc@purestorage.com/>. 
> where a stale LBMS bit state causes `pcie_failed_link_retrain', in the 
> absence of a downstream device, to leave the link stuck at the 2.5GT/s 
> speed rate, which then negatively impacts devices plugged in in the 
> future.
> 
>  See individual change description for further details; 1/4 and 2/4 are 
> new changes, 3/4 supersedes: 
> <https://patchwork.kernel.org/project/linux-pci/patch/alpine.DEB.2.21.2402100045590.2376@angie.orcam.me.uk/>, 
> and 4/4 supersedes: 
> <https://patchwork.kernel.org/project/linux-pci/patch/alpine.DEB.2.21.2402100048440.2376@angie.orcam.me.uk/>.
> 
>  These changes have been verified with a SiFive HiFive Unmatched system, 
> also using a small debug change to verify that the state of the LBMS bit 
> is clear at the exit from `pcie_failed_link_retrain'.
> 
>  Ilpo, since 3/4 and 4/4 have only been trivially updated and their 
> combined effect is not changed even I chose to retain your Reviewed-by 
> tags from v1.  Let me know if you disagree and what to do so you don't.
> 
>  I apologise to take so long, it's been a tough period to me load-wise.

Applied to pci/enumeration for v6.12, thanks for all this debugging
and work.

Matthew, let me know if this addresses the problems you saw, and I can
add your tested-by if appropriate.

Bjorn

      parent reply	other threads:[~2024-08-09 19:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09 13:24 [PATCH v2 0/4] PCI: Rework error reporting with PCIe failed link retraining Maciej W. Rozycki
2024-08-09 13:24 ` [PATCH v2 1/4] PCI: Clear the LBMS bit after a link retrain Maciej W. Rozycki
2024-08-12 10:35   ` Ilpo Järvinen
2024-08-12 14:21     ` Maciej W. Rozycki
2024-08-09 13:24 ` [PATCH v2 2/4] PCI: Revert to the original speed after PCIe failed link retraining Maciej W. Rozycki
2024-08-12 10:36   ` Ilpo Järvinen
2024-08-15  5:57   ` Matthew W Carlis
2024-08-22  9:13   ` Ilpo Järvinen
2024-08-25 13:48     ` Maciej W. Rozycki
2024-08-09 13:24 ` [PATCH v2 3/4] PCI: Correct error reporting with " Maciej W. Rozycki
2024-08-09 13:25 ` [PATCH v2 4/4] PCI: Use an error code " Maciej W. Rozycki
2024-08-09 19:57 ` 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=20240809195727.GA209985@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=mattc@purestorage.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=oohall@gmail.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