Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Nathan Rossi <nathan@nathanrossi.com>
Cc: Lukas Wunner <lukas@wunner.de>,
	linux-pci@vger.kernel.org, Nathan Rossi <nathan.rossi@digi.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH] PCI: Add ACS errata for Pericom PI7C9X2G404 switch
Date: Thu, 9 Sep 2021 12:52:03 -0500	[thread overview]
Message-ID: <20210909175203.GA996100@bjorn-Precision-5520> (raw)
In-Reply-To: <CA+aJhH2v2kJ4qgNTNLQuodLuZ1EzK5Caom_=8U82pUZbOKVE4Q@mail.gmail.com>

On Thu, Sep 09, 2021 at 06:08:33PM +1000, Nathan Rossi wrote:
> On Thu, 9 Sept 2021 at 08:24, Bjorn Helgaas <helgaas@kernel.org> wrote:
> >
> > [+cc Alex, beginning of thread:
> > https://lore.kernel.org/r/20210903034029.306816-1-nathan@nathanrossi.com]
> >
> > On Mon, Sep 06, 2021 at 04:01:20PM +1000, Nathan Rossi wrote:
> > > On Fri, 3 Sept 2021 at 16:18, Lukas Wunner <lukas@wunner.de> wrote:
> > > >
> > > > On Fri, Sep 03, 2021 at 03:40:29AM +0000, Nathan Rossi wrote:
> > > > > The Pericom PI7C9X2G404 PCIe switch has an errata for ACS P2P Request
> > > > > Redirect behaviour when used in the cut-through forwarding mode. The
> > > > > recommended work around for this issue is to use the switch in store and
> > > > > forward mode.
> >
> > Is there a URL for this erratum?  What is the issue?  Does the switch
> 
> Unfortunately the document is not public, it was provided under a NDA.
> However with that said, there is very little additional information in
> the document itself compared to the information provided in the commit
> message/code comments here. The only other information in the document
> that may be applicable is that the whole document is for a number of
> Pericom switch models, however I do not have access to the other two
> switch models and thus cannot validate if this fixup would also apply
> to them.
> 
> For reference the models with PCI IDs:
> - PI7C9X2G404 - 12d8:2404
> - PI7C9X2G304 - 12d8:2304
> - PI7C9X2G303 - 12d8:2303

I assume that running all these models in store and forward mode is
safe, even if it's not the highest-performance config.  If so, I'd
prefer to include all the documented Device IDs in the quirk so people
don't have to stumble over them before we can fix them.

If somebody complains about the performance and can verify that a
device *doesn't* need the quirk, we can remove it then.

Bjorn

      reply	other threads:[~2021-09-09 17:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03  3:40 [PATCH] PCI: Add ACS errata for Pericom PI7C9X2G404 switch Nathan Rossi
2021-09-03  6:18 ` Lukas Wunner
2021-09-06  6:01   ` Nathan Rossi
2021-09-08 22:24     ` Bjorn Helgaas
2021-09-09  8:08       ` Nathan Rossi
2021-09-09 17:52         ` 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=20210909175203.GA996100@bjorn-Precision-5520 \
    --to=helgaas@kernel.org \
    --cc=alex.williamson@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=nathan.rossi@digi.com \
    --cc=nathan@nathanrossi.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