All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Feng Tang <feng.tang@linux.alibaba.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Logan Gunthorpe <logang@deltatee.com>,
	Stephen Bates <sbates@raithlin.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI/P2PDMA: Add Alibaba T-HEAD Yitian 710 to whitelist
Date: Fri, 18 Sep 2026 12:33:53 -0500	[thread overview]
Message-ID: <20260918173353.GA1167671@bhelgaas> (raw)
In-Reply-To: <20260918082412.15967-1-feng.tang@linux.alibaba.com>

On Fri, Sep 18, 2026 at 04:24:12PM +0800, Feng Tang wrote:
> Alibaba T-HEAD Yitian 710 surports PCI peer-to-peer transactions. Add it
> to the P2P whitelist.
> 
> 2 NVME cards with CMB (Command  Memory Buffer) have run p2pmem-test [1]
> fine, under same root complex and different root complexes.
> 
> [1]. https://github.com/sbates130272/p2pmem-test
> 
> Signed-off-by: Feng Tang <feng.tang@linux.alibaba.com>

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

> ---
>  drivers/pci/p2pdma.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/pci/p2pdma.c b/drivers/pci/p2pdma.c
> index c8c414af7078..beb1fe20c9de 100644
> --- a/drivers/pci/p2pdma.c
> +++ b/drivers/pci/p2pdma.c
> @@ -576,6 +576,8 @@ static const struct pci_p2pdma_whitelist_entry {
>  	{PCI_VENDOR_ID_ZHAOXIN, 0x1006, REQ_SAME_HOST_BRIDGE},
>  	{PCI_VENDOR_ID_ZHAOXIN, 0x1007, REQ_SAME_HOST_BRIDGE},
>  	{PCI_VENDOR_ID_ZHAOXIN, 0x1008, 0},
> +	/* Alibaba T-HEAD Yitian 710 CPU */
> +	{PCI_VENDOR_ID_ALIBABA, 0x8000, 0},
>  	{}
>  };
>  
> 
> base-commit: 2ce4ced05cd7b16f3d3430eac021d6184752175f
> -- 
> 2.43.5
> 

      parent reply	other threads:[~2026-09-18 17:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18  8:24 [PATCH] PCI/P2PDMA: Add Alibaba T-HEAD Yitian 710 to whitelist Feng Tang
2026-09-18  8:31 ` sashiko-bot
2026-09-18 15:17 ` Logan Gunthorpe
2026-09-18 17:33 ` 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=20260918173353.GA1167671@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=feng.tang@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=sbates@raithlin.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.