linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Raj, Ashok" <ashok.raj@intel.com>
Cc: Steffen Liebergeld <steffen.liebergeld@kernkonzept.com>,
	linux-pci@vger.kernel.org, stable@vger.kernel.org,
	Andrew Murray <andrew.murray@arm.com>,
	Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH v2] PCI: quirks: Fix register location for UPDCR
Date: Mon, 30 Sep 2019 17:05:41 -0500	[thread overview]
Message-ID: <20190930220541.GA209848@google.com> (raw)
In-Reply-To: <20190927152632.GA4261@otc-nc-03>

On Fri, Sep 27, 2019 at 08:26:32AM -0700, Raj, Ashok wrote:
> On Fri, Sep 27, 2019 at 07:54:57AM -0500, Bjorn Helgaas wrote:
> > [+cc Andrew, Alex, Ashok]
> > 
> > Please cc people who commented on previous versions of a patch.  I
> > added them for you here.
> > 
> > This is probably fine, but I'm waiting to see if Ashok gets a response
> > from the chipset folks.  Hopefully he can ack this as a simple typo
> > fix.
> > 
> > On Wed, Sep 18, 2019 at 03:16:52PM +0200, Steffen Liebergeld wrote:
> > > According to documentation [0] the correct offset for the
> > > Upstream Peer Decode Configuration Register (UPDCR) is 0x1014.
> > > It was previously defined as 0x1114.
> 
> Finally someone in the HW team was able to lookup the documentation and 
> it has stayed at 0x1014 per internal documentation. Apparently the genesis
> is about 10 years ago :-)... so it took some time to hunt this from the team.
> 
> that's the final answer :-)

So I *think* that's an ack for this patch, right?

> > > Commit d99321b63b1f intends to enforce isolation between PCI
> > > devices allowing them to be put into separate IOMMU groups.
> > > Due to the wrong register offset the intended isolation was not
> > > fully enforced. This is fixed with this patch.
> > > 
> > > Please note that I did not test this patch because I have
> > > no hardware that implements this register.
> > > 
> > > [0]
> > > https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/4th-gen-core-family-mobile-i-o-datasheet.pdf
> > > (page 325)
> > > 
> > > Fixes: d99321b63b1f ("PCI: Enable quirks for PCIe ACS on Intel PCH root ports")
> > > Reviewed-by: Andrew Murray <andrew.murray@arm.com>
> > > Signed-off-by: Steffen Liebergeld <steffen.liebergeld@kernkonzept.com>

And I suppose this should have a stable tag.  d99321b63b1f appeared in
v3.15.

I applied this as below to pci/virtualization for v5.5, thanks!

commit e50992e80279
Author: Steffen Liebergeld <steffen.liebergeld@kernkonzept.com>
Date:   Wed Sep 18 15:16:52 2019 +0200

    PCI: Fix Intel ACS quirk UPDCR register address
    
    According to documentation [0] the correct offset for the Upstream Peer
    Decode Configuration Register (UPDCR) is 0x1014.  It was previously defined
    as 0x1114.
    
    d99321b63b1f ("PCI: Enable quirks for PCIe ACS on Intel PCH root ports")
    intended to enforce isolation between PCI devices allowing them to be put
    into separate IOMMU groups.  Due to the wrong register offset the intended
    isolation was not fully enforced.  This is fixed with this patch.
    
    Please note that I did not test this patch because I have no hardware that
    implements this register.
    
    [0] https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/4th-gen-core-family-mobile-i-o-datasheet.pdf (page 325)
    Fixes: d99321b63b1f ("PCI: Enable quirks for PCIe ACS on Intel PCH root ports")
    Link: https://lore.kernel.org/r/7a3505df-79ba-8a28-464c-88b83eefffa6@kernkonzept.com
    Signed-off-by: Steffen Liebergeld <steffen.liebergeld@kernkonzept.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Reviewed-by: Andrew Murray <andrew.murray@arm.com>
    Acked-by: Ashok Raj <ashok.raj@intel.com>
    Cc: stable@vger.kernel.org      # v3.15+

diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index 4e5048cb5ec6..23508c359296 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -4713,7 +4713,7 @@ int pci_dev_specific_acs_enabled(struct pci_dev *dev, u16 acs_flags)
 #define INTEL_BSPR_REG_BPPD  (1 << 9)
 
 /* Upstream Peer Decode Configuration Register */
-#define INTEL_UPDCR_REG 0x1114
+#define INTEL_UPDCR_REG 0x1014
 /* 5:0 Peer Decode Enable bits */
 #define INTEL_UPDCR_REG_MASK 0x3f
 

      reply	other threads:[~2019-09-30 22:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-18 13:16 [PATCH v2] PCI: quirks: Fix register location for UPDCR Steffen Liebergeld
2019-09-27 12:54 ` Bjorn Helgaas
2019-09-27 15:26   ` Raj, Ashok
2019-09-30 22:05     ` 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=20190930220541.GA209848@google.com \
    --to=helgaas@kernel.org \
    --cc=alex.williamson@redhat.com \
    --cc=andrew.murray@arm.com \
    --cc=ashok.raj@intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=steffen.liebergeld@kernkonzept.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).