linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vadim Lomovtsev <Vadim.Lomovtsev@caviumnetworks.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, alex.williamson@redhat.com,
	Wilson.Snyder@cavium.com, robert.richter@cavium.com,
	david.daney@cavium.com, mjaggi@caviumnetworks.com,
	Vadim Lomovtsev <Vadim.Lomovtsev@cavium.com>
Subject: Re: [PATCH v7 0/2] PCI: quirks: Cavium ThunderX ACS quirk update
Date: Fri, 20 Oct 2017 03:44:29 -0700	[thread overview]
Message-ID: <20171020104429.GA7898@localhost.localdomain> (raw)
In-Reply-To: <20171019185010.GE6332@bhelgaas-glaptop.roam.corp.google.com>

On Thu, Oct 19, 2017 at 01:50:10PM -0500, Bjorn Helgaas wrote:
> On Thu, Oct 19, 2017 at 04:59:21AM -0700, Vadim Lomovtsev wrote:
> > On Thu, Oct 19, 2017 at 06:26:45AM -0500, Bjorn Helgaas wrote:
> > > On Tue, Oct 17, 2017 at 05:47:37AM -0700, Vadim Lomovtsev wrote:
> > > > From: Vadim Lomovtsev <Vadim.Lomovtsev@cavium.com>
> > > > 
> > > > version 7:
> > > > - update patch description accordingly to review comments;
> > > > - split for two patches: for ACS mask change and device id match change;
> > > > - remove macro #define of ACS flags, put it back to quirk function;
> > > > - remove '__inline_' from device id matching function;
> > > > - wrap code comments to fit into 80 columns;
> > > > - comment fix: change 0xa00 to 0xf800 for matching function description;
> > > > 
> > > > version 6:
> > > > - comment typo fix: change 0xa00 to 0xa000;
> > > > 
> > > > version 5:
> > > > - update code comments accordingly to review comments;
> > > > 
> > > > version 4:
> > > > - update ACS mask (remove TB and TD bits), update commit message (remove
> > > >   ACS register printout);
> > > > 
> > > > version 3:
> > > > - update subject: remove CN8XXX from subject line, replace it with ThunderX;
> > > > 
> > > > version 2:
> > > > - update match function in order to filter only ThunderX devices by device
> > > >   ids to properly filter CN8XXX devices, update subject & description with
> > > >   ACS register info (v2 was rejected by maillist due to triple X in subject);
> > > >   
> > > > Vadim Lomovtsev (2):
> > > >   PCI: quirks: Set Cavium ACS capability quirk flags to assert
> > > >     RR/CR/SV/UF.
> > > >   PCI: quirks: Apply Cavium ThunderX ACS quirk only to Root Ports
> > > > 
> > > >  drivers/pci/quirks.c | 26 ++++++++++++++++++++------
> > > >  1 file changed, 20 insertions(+), 6 deletions(-)
> > > 
> > > If I'm reading this correctly, the first patch is basically fixing a bug in
> > > the original Cavium ACS quirk (b404bcfbf035 ("PCI: Add ACS quirk for all
> > > Cavium devices")).  Right?
> > 
> > Yes, first patch fixes improper ACS flags in the patch you mentioned.
> > 
> > The second one fixes devid check from another patch
> > (b77d537d00d0 PCI: Apply Cavium ACS quirk only to CN81xx/CN83xx/CN88xx devices).
> > 
> > > 
> > > I put them on pci/virtualization for v4.15 as follows (patches unchanged,
> > > changelogs wordsmithed).
> > >
> > 
> > Good, thank you.
> > 
> > > You mentioned stable backports.  b404bcfbf035 ("PCI: Add ACS quirk for all
> > > Cavium devices") appeared in v4.6.  b77d537d00d0 ("PCI: Apply Cavium ACS
> > > quirk only to CN81xx/CN83xx/CN88xx devices") appeared in v4.12.  I assume
> > > you would ideally want all this backported as far as v4.6?  We'd have to
> > > figure out how to express that in stable tags.
> > 
> > Ideally yes, I think we would need to have them backported onto stable(s),
> > but so far I didn't see any bug-reports which could require these fixes.
> > 
> > Anyway, in term of backporting them - are there anything I can help with ?
> 
> I added the following tags, which I *think* should be sufficient:
> 
>   PCI: Set Cavium ACS capability quirk flags to assert RR/CR/SV/UF
>   Cc: stable@vger.kernel.org      # v4.6+: b77d537d00d0: PCI: Apply Cavium ACS quirk only to CN81xx/CN83xx/CN88xx devices
> 
>   PCI: Apply Cavium ThunderX ACS quirk to more Root Ports
>   Cc: stable@vger.kernel.org      # v4.12+

Looks good. Thank you.

-Vadim

      reply	other threads:[~2017-10-20 10:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-12 11:55 [PATCH] PCI: quirks: update cavium ACS quirk implementation Vadim Lomovtsev
2017-09-12 16:15 ` Alex Williamson
2017-09-13 11:37   ` Vadim Lomovtsev
2017-09-13 12:01   ` Vadim Lomovtsev
2017-09-15 12:57 ` [PATCH v3] PCI: quirks: update Cavium ThunderX " Vadim Lomovtsev
2017-09-15 19:20   ` Lomovtsev, Vadim
2017-09-18  8:48   ` [PATCH v4] " Vadim Lomovtsev
2017-09-20 11:33     ` Vadim Lomovtsev
2017-09-20 16:31     ` Alex Williamson
2017-09-21  8:39       ` Vadim Lomovtsev
2017-09-25 13:08     ` [PATCH v5] " Vadim Lomovtsev
2017-09-26 15:23       ` Vadim Lomovtsev
2017-09-26 15:43       ` Alex Williamson
2017-09-26 16:00         ` Vadim Lomovtsev
2017-09-27 18:03           ` Vadim Lomovtsev
2017-09-27 18:20       ` [PATCH v6] " Vadim Lomovtsev
2017-09-27 20:03         ` Vadim Lomovtsev
2017-09-27 20:18         ` Alex Williamson
2017-09-29 12:22           ` Vadim Lomovtsev
2017-10-09 16:14           ` Vadim Lomovtsev
2017-10-12 13:27         ` Robert Richter
2017-10-16 21:23         ` Bjorn Helgaas
2017-10-17 11:29           ` Vadim Lomovtsev
2017-10-17 12:47         ` [PATCH v7 0/2] PCI: quirks: Cavium ThunderX ACS quirk update Vadim Lomovtsev
2017-10-17 12:47           ` [PATCH v7 1/2] PCI: quirks: Set Cavium ACS capability quirk flags to assert RR/CR/SV/UF Vadim Lomovtsev
2017-10-17 12:47           ` [PATCH v7 2/2] PCI: quirks: Apply Cavium ThunderX ACS quirk only to Root Ports Vadim Lomovtsev
2017-10-19 11:26           ` [PATCH v7 0/2] PCI: quirks: Cavium ThunderX ACS quirk update Bjorn Helgaas
2017-10-19 11:59             ` Vadim Lomovtsev
2017-10-19 18:50               ` Bjorn Helgaas
2017-10-20 10:44                 ` Vadim Lomovtsev [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=20171020104429.GA7898@localhost.localdomain \
    --to=vadim.lomovtsev@caviumnetworks.com \
    --cc=Vadim.Lomovtsev@cavium.com \
    --cc=Wilson.Snyder@cavium.com \
    --cc=alex.williamson@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=david.daney@cavium.com \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mjaggi@caviumnetworks.com \
    --cc=robert.richter@cavium.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;
as well as URLs for NNTP newsgroup(s).