All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-pci@vger.kernel.org, donald.d.dugger@intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: Add Wellsburg (X99) to Intel PCH root port ACS quirk
Date: Fri, 23 Jan 2015 17:18:14 -0600	[thread overview]
Message-ID: <20150123231814.GT29776@google.com> (raw)
In-Reply-To: <20150122181524.1586.14496.stgit@gimli.home>

On Thu, Jan 22, 2015 at 11:15:43AM -0700, Alex Williamson wrote:
> Intel has confirmed that the Wellsburg chipset, while not reporting
> ACS, does provide the proper isolation through the RCBA/BSPR
> registers, so the same quirk works for this set of device IDs.
> 
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> Cc: Don Dugger <donald.d.dugger@intel.com>

Applied with Don's ack to pci/virtualization for v3.20, thanks!

> ---
> 
>  drivers/pci/quirks.c |    3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index ed6f89b..2cdb789 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -3630,6 +3630,9 @@ static const u16 pci_quirk_intel_pch_acs_ids[] = {
>  	0x9c98, 0x9c99, 0x9c9a, 0x9c9b,
>  	/* Patsburg (X79) PCH */
>  	0x1d10, 0x1d12, 0x1d14, 0x1d16, 0x1d18, 0x1d1a, 0x1d1c, 0x1d1e,
> +	/* Wellsburg (X99) PCH */
> +	0x8d10, 0x8d11, 0x8d12, 0x8d13, 0x8d14, 0x8d15, 0x8d16, 0x8d17,
> +	0x8d18, 0x8d19, 0x8d1a, 0x8d1b, 0x8d1c, 0x8d1d, 0x8d1e,
>  };
>  
>  static bool pci_quirk_intel_pch_acs_match(struct pci_dev *dev)
> 

      parent reply	other threads:[~2015-01-23 23:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22 18:15 [PATCH] PCI: Add Wellsburg (X99) to Intel PCH root port ACS quirk Alex Williamson
2015-01-22 19:44 ` Dugger, Donald D
2015-01-22 19:44   ` Dugger, Donald D
2015-01-23 23:18 ` 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=20150123231814.GT29776@google.com \
    --to=bhelgaas@google.com \
    --cc=alex.williamson@redhat.com \
    --cc=donald.d.dugger@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.