netdev - Re: [PATCH net-next v4] idpf: add support for IDPF PCI programming interface

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: <2aec7267-32de-4984-a628-e9f8286cdfa3@intel.com>
Date: Thu, 4 Sep 2025 11:05:24 -0700
From: "Linga, Pavan Kumar" <pavan.kumar.linga@...el.com>
To: Simon Horman <horms@...nel.org>
CC: <intel-wired-lan@...ts.osuosl.org>, <madhu.chittim@...el.com>,
	<netdev@...r.kernel.org>, Sridhar Samudrala <sridhar.samudrala@...el.com>
Subject: Re: [PATCH net-next v4] idpf: add support for IDPF PCI programming
 interface



On 9/3/2025 5:51 AM, Simon Horman wrote:
> On Tue, Sep 02, 2025 at 08:58:52PM -0700, Pavan Kumar Linga wrote:
>> At present IDPF supports only 0x1452 and 0x145C as PF and VF device IDs
>> on our current generation hardware. Future hardware exposes a new set of
>> device IDs for each generation. To avoid adding a new device ID for each
>> generation and to make the driver forward and backward compatible,
>> make use of the IDPF PCI programming interface to load the driver.
>>
>> Write and read the VF_ARQBAL mailbox register to find if the current
>> device is a PF or a VF.
>>
>> PCI SIG allocated a new programming interface for the IDPF compliant
>> ethernet network controller devices. It can be found at:
>> https://members.pcisig.com/wg/PCI-SIG/document/20113
>> with the document titled as 'PCI Code and ID Assignment Revision 1.16'
>> or any latest revisions.
>>
>> Tested this patch by doing a simple driver load/unload on Intel IPU E2000
>> hardware which supports 0x1452 and 0x145C device IDs and new hardware
>> which supports the IDPF PCI programming interface.
>>
>> Reviewed-by: Sridhar Samudrala <sridhar.samudrala@...el.com>
>> Signed-off-by: Madhu Chittim <madhu.chittim@...el.com>
>> Reviewed-by: Simon Horman <horms@...nel.org>
>> Signed-off-by: Pavan Kumar Linga <pavan.kumar.linga@...el.com>
> 
> Hi Pavan,
> 
> Should this be targeted at iwl, where it applies cleanly,
> rather than net-next, where it does not.
> 
> If the later, I think that a rebase and repost is appropriate.
> 
> ...

My bad. It is targeted for iwl-next, but I marked it as net-next.

Please let me know if you want me to correct the target and send a new 
revision.

Thanks,
Pavan