mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: LeoLiu-oc <leoliu-oc@zhaoxin.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Logan Gunthorpe <logang@deltatee.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Eros Zhang <eroszhang@zhaoxin.com>,
	Cobe Chen <cobechen@zhaoxin.com>,
	"Tony W . Wang" <tonywwang@zhaoxin.com>
Subject: Re: [PATCH] PCI/P2PDMA: Add Zhaoxin host bridges to whitelist
Date: Thu, 3 Sep 2026 17:17:52 -0500	[thread overview]
Message-ID: <20260903221752.GA2266182@bhelgaas> (raw)
In-Reply-To: <20260901083653.48890-1-leoliu-oc@zhaoxin.com>

On Tue, Sep 01, 2026 at 04:36:53PM +0800, LeoLiu-oc wrote:
> Zhaoxin host bridges support peer-to-peer DMA. Add their device IDs
> (0x1003, 0x1005-0x1008) to the whitelist so that p2pdma works on these
> platforms.
> 
> The entries cover the KX-6000, KH-40000, KX-6000G, KX-7000 and KH-50000
> families.
> 
> The KX-6000/KH-40000/KX-6000G/KX-7000 entries are marked
> REQ_SAME_HOST_BRIDGE because P2P requests crossing different host bridges
> are not supported on these parts. The KH-50000 entry is whitelisted
> without this restriction.
> 
> Signed-off-by: LeoLiu-oc <leoliu-oc@zhaoxin.com>

Applied to pci/p2pdma for v7.4, thank you!

> ---
>  drivers/pci/p2pdma.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/drivers/pci/p2pdma.c b/drivers/pci/p2pdma.c
> index 9334eb314663..9fbbf1692f0e 100644
> --- a/drivers/pci/p2pdma.c
> +++ b/drivers/pci/p2pdma.c
> @@ -569,6 +569,12 @@ static const struct pci_p2pdma_whitelist_entry {
>  	{PCI_VENDOR_ID_NVIDIA, 0x2f96, 0},
>  	{PCI_VENDOR_ID_NVIDIA, 0x2f97, 0},
>  	{PCI_VENDOR_ID_NVIDIA, 0x2f98, 0},
> +	/* Zhaoxin KX-6000/KH-40000/KX-6000G/KX-7000/KH-50000 */
> +	{PCI_VENDOR_ID_ZHAOXIN, 0x1003, REQ_SAME_HOST_BRIDGE},
> +	{PCI_VENDOR_ID_ZHAOXIN, 0x1005, REQ_SAME_HOST_BRIDGE},
> +	{PCI_VENDOR_ID_ZHAOXIN, 0x1006, REQ_SAME_HOST_BRIDGE},
> +	{PCI_VENDOR_ID_ZHAOXIN, 0x1007, REQ_SAME_HOST_BRIDGE},
> +	{PCI_VENDOR_ID_ZHAOXIN, 0x1008, 0},
>  	{}
>  };
>  
> -- 
> 2.43.0
> 
> 

      reply	other threads:[~2026-09-03 22:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01  8:36 LeoLiu-oc
2026-09-03 22:17 ` 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=20260903221752.GA2266182@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=cobechen@zhaoxin.com \
    --cc=eroszhang@zhaoxin.com \
    --cc=leoliu-oc@zhaoxin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=tonywwang@zhaoxin.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

all inboxes | Powered by JetHome®