From: Logan Gunthorpe <logang@deltatee.com>
To: Andrew Maier <andrew.maier@eideticom.com>,
bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Armen Baloyan <abaloyan@gigaio.com>
Subject: Re: [PATCH v2] PCI/P2PDMA: Add the remaining Intel Sky Lake-E root ports to the whitelist
Date: Fri, 7 Feb 2020 15:20:35 -0700 [thread overview]
Message-ID: <a70eb8eb-c584-0a53-07a9-9078b68712e4@deltatee.com> (raw)
In-Reply-To: <20200207221219.4309-1-andrew.maier@eideticom.com>
+cc Armen
On 2020-02-07 3:12 p.m., Andrew Maier wrote:
> Add the three remaining Intel Sky Lake-E host root ports to the
> whitelist of p2pdma.
>
> P2P has been tested and is working on this system.
>
> Signed-off-by: Andrew Maier <andrew.maier@eideticom.com>
> ---
> Resending this as I rebased it onto the latest patches.
Right, this is the same machine Armen already sent, so I've CC'd him.
Looks like we're just adding the extra possible root ports from the PCI
IDs database:
2031 Sky Lake-E PCI Express Root Port B
2032 Sky Lake-E PCI Express Root Port C
2033 Sky Lake-E PCI Express Root Port D
Makes sense to me, thanks,
Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
> drivers/pci/p2pdma.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/pci/p2pdma.c b/drivers/pci/p2pdma.c
> index 9a8a38384121..b73b10bce0df 100644
> --- a/drivers/pci/p2pdma.c
> +++ b/drivers/pci/p2pdma.c
> @@ -291,6 +291,9 @@ static const struct pci_p2pdma_whitelist_entry {
> {PCI_VENDOR_ID_INTEL, 0x2f01, REQ_SAME_HOST_BRIDGE},
> /* Intel SkyLake-E */
> {PCI_VENDOR_ID_INTEL, 0x2030, 0},
> + {PCI_VENDOR_ID_INTEL, 0x2031, 0},
> + {PCI_VENDOR_ID_INTEL, 0x2032, 0},
> + {PCI_VENDOR_ID_INTEL, 0x2033, 0},
> {PCI_VENDOR_ID_INTEL, 0x2020, 0},
> {}
> };
>
next prev parent reply other threads:[~2020-02-07 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 22:12 [PATCH v2] PCI/P2PDMA: Add the remaining Intel Sky Lake-E root ports to the whitelist Andrew Maier
2020-02-07 22:20 ` Logan Gunthorpe [this message]
2020-03-18 23:13 ` Bjorn Helgaas
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=a70eb8eb-c584-0a53-07a9-9078b68712e4@deltatee.com \
--to=logang@deltatee.com \
--cc=abaloyan@gigaio.com \
--cc=andrew.maier@eideticom.com \
--cc=bhelgaas@google.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 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).