linux-kernel - RE: [PATCH] PCI/P2PDMA: Update device table with 3rd gen Xeon platform information

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <cde2aa29568a42418ee9cdc2616a2138@intel.com>
Date:   Fri, 25 Feb 2022 19:14:03 +0000
From:   "Ruhl, Michael J" <michael.j.ruhl@...el.com>
To:     Bjorn Helgaas <helgaas@...nel.org>
CC:     "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "bhelgaas@...gle.com" <bhelgaas@...gle.com>,
        "logang@...tatee.com" <logang@...tatee.com>,
        "Williams, Dan J" <dan.j.williams@...el.com>
Subject: RE: [PATCH] PCI/P2PDMA: Update device table with 3rd gen Xeon
 platform information

>-----Original Message-----
>From: Bjorn Helgaas <helgaas@...nel.org>
>Sent: Friday, February 25, 2022 12:10 PM
>To: Ruhl, Michael J <michael.j.ruhl@...el.com>
>Cc: linux-pci@...r.kernel.org; linux-kernel@...r.kernel.org;
>bhelgaas@...gle.com; logang@...tatee.com; Williams, Dan J
><dan.j.williams@...el.com>
>Subject: Re: [PATCH] PCI/P2PDMA: Update device table with 3rd gen Xeon
>platform information
>
>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@...el.com>
>> Signed-off-by: Michael J. Ruhl <michael.j.ruhl@...el.com>
>
>Updated the commit log to match previous similar patches and applied
>as below to pci/p2pdma for v5.18, thanks!

Thank you!

>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.

I will see about getting this updated asap.

Regards,

M

>Bjorn
>
>
>  commit feaea1fe8b36 ("PCI/P2PDMA: Add Intel 3rd Gen Intel Xeon Scalable
>Processors to whitelist")
>  Author: Michael J. Ruhl <michael.j.ruhl@...el.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@...el.com
>    Signed-off-by: Michael J. Ruhl <michael.j.ruhl@...el.com>
>    Signed-off-by: Bjorn Helgaas <bhelgaas@...gle.com>
>    Reviewed-by: Dan Williams <dan.j.williams@...el.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
>>