netdev - Re: bnxt_en: Incorrect tx timestamp report

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <8f128d86-a39c-4699-800a-67084671e853@intel.com>
Date: Thu, 20 Mar 2025 10:11:35 -0700
From: Jacob Keller <jacob.e.keller@...el.com>
To: Kamil Zaripov <zaripov-kamil@...ide.ai>, <netdev@...r.kernel.org>
Subject: Re: bnxt_en: Incorrect tx timestamp report

On 3/20/2025 7:35 AM, Kamil Zaripov wrote:
> 1. Would it be beneficial to modify the bnxt_en driver to create only a single PHC Linux device for network cards that physically have only one PHC?
> 

That depends. If it has only one underlying clock, but each PF has its
own register space, it may functionally be independent clocks in
practice. I don't know the bnxt_en driver or hardware well enough to
know if that is the case.

If it really is one clock with one set of registers to control it, then
it should only expose one PHC. This may be tricky depending on the
driver design. (See ice as an example where we've had a lot of
challenges in this space because of the multiple PFs)