From: Bjorn Helgaas <bhelgaas@google.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-pci@vger.kernel.org, john.ronciak@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: Add ACS quirks for Intel I219-LM/V
Date: Tue, 11 Aug 2015 15:28:34 -0500 [thread overview]
Message-ID: <20150811202834.GH13982@google.com> (raw)
In-Reply-To: <20150810183055.5714.12998.stgit@gimli.home>
On Mon, Aug 10, 2015 at 12:32:04PM -0600, Alex Williamson wrote:
> The Intel 100-series chipset now includes the integrated Ethernet as
> part of a multifunction package. The Ethernet function does not
> include native ACS support, but Intel confirms that the device is not
> capable of peer-to-peer within the package. We can therefore quirk it
> to expose the isolation.
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> Cc: John Ronciak <john.ronciak@intel.com>
Applied with John's ack to pci/virtualization for v4.3, thanks!
> ---
> drivers/pci/quirks.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index e9fd0e9..a914848 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -3848,6 +3848,9 @@ static const struct pci_dev_acs_enabled {
> { PCI_VENDOR_ID_INTEL, 0x105F, pci_quirk_mf_endpoint_acs },
> { PCI_VENDOR_ID_INTEL, 0x1060, pci_quirk_mf_endpoint_acs },
> { PCI_VENDOR_ID_INTEL, 0x10D9, pci_quirk_mf_endpoint_acs },
> + /* I219 */
> + { PCI_VENDOR_ID_INTEL, 0x15b7, pci_quirk_mf_endpoint_acs },
> + { PCI_VENDOR_ID_INTEL, 0x15b8, pci_quirk_mf_endpoint_acs },
> /* Intel PCH root ports */
> { PCI_VENDOR_ID_INTEL, PCI_ANY_ID, pci_quirk_intel_pch_acs },
> { 0x19a2, 0x710, pci_quirk_mf_endpoint_acs }, /* Emulex BE3-R */
>
prev parent reply other threads:[~2015-08-11 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 18:32 [PATCH] PCI: Add ACS quirks for Intel I219-LM/V Alex Williamson
2015-08-10 19:52 ` John Ronciak
2015-08-11 20:28 ` 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=20150811202834.GH13982@google.com \
--to=bhelgaas@google.com \
--cc=alex.williamson@redhat.com \
--cc=john.ronciak@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.