All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: kai zhang <zhangkai.cool@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Logan Gunthorpe <logang@deltatee.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI/P2PDMA: Add Intel 0x6f00 host bridge to the whitelist
Date: Wed, 7 Oct 2026 16:59:36 -0500	[thread overview]
Message-ID: <20261007215936.GA847773@bhelgaas> (raw)
In-Reply-To: <20261007141558.59852-1-zhangkai.cool@gmail.com>

On Wed, Oct 07, 2026 at 10:15:58PM +0800, kai zhang wrote:
> For P2P paths routed through a host bridge, the P2PDMA core consults a
> whitelist of known-good hardware. Add Intel 8086:6f00 with
> REQ_SAME_HOST_BRIDGE so the entry permits peers only below the same host
> bridge.
> 
> The bridge was tested on a single-socket Intel Xeon E5-2697A v4 system
> with two PCIe GPUs below different Root Ports of the same host bridge.
> Without the whitelist entry, peer access was rejected before a transfer
> was issued. With the entry, 64 MiB peer transfers completed in both
> directions with data integrity verified while the IOMMU used translated
> mode.
> 
> Assisted-by: LLM
> Signed-off-by: kai zhang <zhangkai.cool@gmail.com>

Applied to pci/p2pdma for v7.4, thanks!

> ---
>  drivers/pci/p2pdma.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/pci/p2pdma.c b/drivers/pci/p2pdma.c
> index 9334eb314663..84413920e39b 100644
> --- a/drivers/pci/p2pdma.c
> +++ b/drivers/pci/p2pdma.c
> @@ -542,6 +542,7 @@ static const struct pci_p2pdma_whitelist_entry {
>  	/* Intel Xeon E5/Core i7 */
>  	{PCI_VENDOR_ID_INTEL,	0x3c00, REQ_SAME_HOST_BRIDGE},
>  	{PCI_VENDOR_ID_INTEL,	0x3c01, REQ_SAME_HOST_BRIDGE},
> +	{PCI_VENDOR_ID_INTEL,	0x6f00, REQ_SAME_HOST_BRIDGE},
>  	/* Intel Xeon E7 v3/Xeon E5 v3/Core i7 */
>  	{PCI_VENDOR_ID_INTEL,	0x2f00, REQ_SAME_HOST_BRIDGE},
>  	{PCI_VENDOR_ID_INTEL,	0x2f01, REQ_SAME_HOST_BRIDGE},
> -- 
> 2.54.0 (Apple Git-157)
> 

      parent reply	other threads:[~2026-10-07 21:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 14:15 [PATCH] PCI/P2PDMA: Add Intel 0x6f00 host bridge to the whitelist kai zhang
2026-10-07 14:18 ` sashiko-bot
2026-10-07 21:59 ` 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=20261007215936.GA847773@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=zhangkai.cool@gmail.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 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.