All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>,
	Logan Gunthorpe <logang@deltatee.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI/P2PDMA: Add Nvidia Vera Rubin device to P2P whitelist
Date: Wed, 22 Jul 2026 08:32:48 +0300	[thread overview]
Message-ID: <20260722053248.GQ110966@unreal> (raw)
In-Reply-To: <20260705-p2p-vr-v1-1-3cd45cab3fb4@nvidia.com>

On Sun, Jul 05, 2026 at 12:54:07PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
> 
> Nvidia Vera Rubin platforms support PCI peer‑to‑peer transactions.
> Add them to the P2P whitelist to enable this functionality.
> 
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> ---
>  drivers/pci/p2pdma.c | 5 +++++
>  1 file changed, 5 insertions(+)

Bjorn,

Is anything else missing? Can you please merge it?

Thanks

> 
> diff --git a/drivers/pci/p2pdma.c b/drivers/pci/p2pdma.c
> index b2d5266f8653..9334eb314663 100644
> --- a/drivers/pci/p2pdma.c
> +++ b/drivers/pci/p2pdma.c
> @@ -564,6 +564,11 @@ static const struct pci_p2pdma_whitelist_entry {
>  	{PCI_VENDOR_ID_INTEL,	PCI_DEVICE_ID_INTEL_QAT_6XXX, 0},
>  	/* Google SoCs. */
>  	{PCI_VENDOR_ID_GOOGLE,	PCI_ANY_ID, 0},
> +	/* Nvidia CPUs */
> +	{PCI_VENDOR_ID_NVIDIA, 0x2f95, 0},
> +	{PCI_VENDOR_ID_NVIDIA, 0x2f96, 0},
> +	{PCI_VENDOR_ID_NVIDIA, 0x2f97, 0},
> +	{PCI_VENDOR_ID_NVIDIA, 0x2f98, 0},
>  	{}
>  };
>  
> 
> ---
> base-commit: dc59e4fea9d83f03bad6bddf3fa2e52491777482
> change-id: 20260615-p2p-vr-514bd262a839
> 
> Best regards,
> --  
> Leon Romanovsky <leonro@nvidia.com>
> 
> 

  parent reply	other threads:[~2026-07-22  5:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-05  9:54 [PATCH] PCI/P2PDMA: Add Nvidia Vera Rubin device to P2P whitelist Leon Romanovsky
2026-07-05  9:56 ` sashiko-bot
2026-07-06 15:35 ` Logan Gunthorpe
2026-07-22  5:32 ` Leon Romanovsky [this message]
2026-07-22 17:43 ` 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=20260722053248.GQ110966@unreal \
    --to=leon@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=logang@deltatee.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.