public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Yazen Ghannam <yazen.ghannam@amd.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org,  Lukas Wunner <lukas@wunner.de>,
	Borislav Petkov <bp@alien8.de>,
	 linux-edac@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	 linuxppc-dev@lists.ozlabs.org,
	Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
	 Oliver O'Halloran <oohall@gmail.com>,
	Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH 0/3] PCI: Add support for logging Flit Mode TLPs (PCIe6)
Date: Wed, 18 Dec 2024 16:24:53 +0200 (EET)	[thread overview]
Message-ID: <bbd52a2b-a97f-7825-c271-0f470b75df1b@linux.intel.com> (raw)
In-Reply-To: <20241217214929.GA1121691@yaz-khff2.amd.com>

[-- Attachment #1: Type: text/plain, Size: 2496 bytes --]

On Tue, 17 Dec 2024, Yazen Ghannam wrote:

> On Fri, Jun 14, 2024 at 06:09:18PM +0300, Ilpo Järvinen wrote:
> > This series adds support for Flit Mode (PCIe6). The series is built on
> > top of the TLP Logging refactoring series:
> > 
> >   https://lore.kernel.org/linux-pci/20240514113109.6690-1-ilpo.jarvinen@linux.intel.com/
> > 
> > Important note to maintainer: The series carries
> > pcie_update_link_speed() refactoring change that is almost identical
> > with a patch in the PCIe BW controller series. The patch itself is
> > basically the same but the context has minor difference. This will need
> > to be considered if applying both series within the same kernel cycle.
> > 
> > Ilpo Järvinen (3):
> >   PCI: Refactor pcie_update_link_speed()
> >   PCI: Track Flit Mode Status & print it with link status
> >   PCI: Handle TLP Log in Flit mode
> > 
> >  drivers/pci/hotplug/pciehp_hpc.c |  5 +--
> >  drivers/pci/pci.c                | 12 ++++---
> >  drivers/pci/pci.h                | 13 ++++++--
> >  drivers/pci/pcie/aer.c           |  4 ++-
> >  drivers/pci/pcie/dpc.c           | 23 ++++++++++---
> >  drivers/pci/pcie/tlp.c           | 57 ++++++++++++++++++++++----------
> >  drivers/pci/probe.c              | 13 +++++---
> >  include/linux/aer.h              | 13 ++++++--
> >  include/linux/pci.h              |  1 +
> >  include/ras/ras_event.h          | 12 +++----
> >  include/uapi/linux/pci_regs.h    |  6 +++-
> >  11 files changed, 112 insertions(+), 47 deletions(-)
>
> Is there any new development on this feature? Or is it on hold while any
> spec oversights are worked out in the PCI-SIG?

As far as I know, the series is not on hold. It just tends to take time 
from Bjorn to get patches applied (and I don't want to pressure 
maintainers with frequent pings). But I think it might help if you would 
kindly review the patches. :-)

And of course this series depends on the TLP cleanup series that has to 
be applied first (but hopefully that happens soon enough).

When it comes to the spec oversight, we concluded with Lukas Wunner that 
even if DPC capability would eventually get a flag to indicate in which 
mode the TLP was logged we cannot assume the flags is always there. Thus, 
this link Flit mode status tracking has to be done anyway. I know it's not 
ideal because at least in theory the state kept by the kernel could be 
stale but there seems to no way around that given how the spec is.

-- 
 i.

      reply	other threads:[~2024-12-18 14:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14 15:09 [PATCH 0/3] PCI: Add support for logging Flit Mode TLPs (PCIe6) Ilpo Järvinen
2024-06-14 15:09 ` [PATCH 1/3] PCI: Refactor pcie_update_link_speed() Ilpo Järvinen
2024-06-14 15:09 ` [PATCH 2/3] PCI: Track Flit Mode Status & print it with link status Ilpo Järvinen
2024-06-14 15:09 ` [PATCH 3/3] PCI: Handle TLP Log in Flit mode Ilpo Järvinen
2024-12-17 21:49 ` [PATCH 0/3] PCI: Add support for logging Flit Mode TLPs (PCIe6) Yazen Ghannam
2024-12-18 14:24   ` Ilpo Järvinen [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=bbd52a2b-a97f-7825-c271-0f470b75df1b@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lukas@wunner.de \
    --cc=mahesh@linux.ibm.com \
    --cc=oohall@gmail.com \
    --cc=tony.luck@intel.com \
    --cc=yazen.ghannam@amd.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