public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Michael J. Ruhl" <michael.j.ruhl@intel.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	bhelgaas@google.com, logang@deltatee.com,
	dan.j.williams@intel.com
Subject: Re: [PATCH] PCI/P2PDMA: Update device table with 3rd gen Xeon platform information
Date: Fri, 25 Feb 2022 11:09:44 -0600	[thread overview]
Message-ID: <20220225170944.GA364325@bhelgaas> (raw)
In-Reply-To: <20220209162801.7647-1-michael.j.ruhl@intel.com>

On Wed, Feb 09, 2022 at 11:28:01AM -0500, Michael J. Ruhl wrote:
> In order to do P2P communication the bridge ID of the platform
> must be in the P2P device table.
> 
> Update the P2P device table with a device id for the 3rd Gen
> Intel Xeon Scalable Processors.
> 
> Reviewed-by: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Michael J. Ruhl <michael.j.ruhl@intel.com>

Updated the commit log to match previous similar patches and applied
as below to pci/p2pdma for v5.18, thanks!

Device ID 0x09a2 doesn't appear at https://pci-ids.ucw.cz/read/PC/8086
which means "lspci" won't be able to display a human-readable name for
these devices.  You can easily add a name at that same URL.

Bjorn


  commit feaea1fe8b36 ("PCI/P2PDMA: Add Intel 3rd Gen Intel Xeon Scalable Processors to whitelist")
  Author: Michael J. Ruhl <michael.j.ruhl@intel.com>
  Date:   Wed Feb 9 11:28:01 2022 -0500

    PCI/P2PDMA: Add Intel 3rd Gen Intel Xeon Scalable Processors to whitelist
    
    In order to do P2P communication the bridge ID of the platform must be in
    the P2P device table.
    
    Update the P2P device table with a device ID for the 3rd Gen Intel Xeon
    Scalable Processors.
    
    Link: https://lore.kernel.org/r/20220209162801.7647-1-michael.j.ruhl@intel.com
    Signed-off-by: Michael J. Ruhl <michael.j.ruhl@intel.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Reviewed-by: Dan Williams <dan.j.williams@intel.com>

> ---
>  drivers/pci/p2pdma.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/pci/p2pdma.c b/drivers/pci/p2pdma.c
> index 1015274bd2fe..30b1df3c9d2f 100644
> --- a/drivers/pci/p2pdma.c
> +++ b/drivers/pci/p2pdma.c
> @@ -321,6 +321,7 @@ static const struct pci_p2pdma_whitelist_entry {
>  	{PCI_VENDOR_ID_INTEL,	0x2032, 0},
>  	{PCI_VENDOR_ID_INTEL,	0x2033, 0},
>  	{PCI_VENDOR_ID_INTEL,	0x2020, 0},
> +	{PCI_VENDOR_ID_INTEL,	0x09a2, 0},
>  	{}
>  };
>  
> -- 
> 2.31.1
> 

  parent reply	other threads:[~2022-02-25 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 16:28 [PATCH] PCI/P2PDMA: Update device table with 3rd gen Xeon platform information Michael J. Ruhl
2022-02-25 15:49 ` Ruhl, Michael J
2022-02-25 17:09 ` Bjorn Helgaas [this message]
2022-02-25 19:14   ` Ruhl, Michael J

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=20220225170944.GA364325@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=michael.j.ruhl@intel.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