netdev - RE: [Intel-wired-lan] [PATCH iwl-next v12 06/14] iavf: add initial framework for registering PTP clock

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: <SJ0PR11MB58654C9766759707F71DC9F78F512@SJ0PR11MB5865.namprd11.prod.outlook.com>
Date: Mon, 4 Nov 2024 11:00:28 +0000
From: "Romanowski, Rafal" <rafal.romanowski@...el.com>
To: "Polchlopek, Mateusz" <mateusz.polchlopek@...el.com>,
	"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "Keller, Jacob E"
	<jacob.e.keller@...el.com>, "Drewek, Wojciech" <wojciech.drewek@...el.com>,
	Sai Krishna <saikrishnag@...vell.com>, Simon Horman <horms@...nel.org>,
	"Zaki, Ahmed" <ahmed.zaki@...el.com>, "Polchlopek, Mateusz"
	<mateusz.polchlopek@...el.com>
Subject: RE: [Intel-wired-lan] [PATCH iwl-next v12 06/14] iavf: add initial
 framework for registering PTP clock

> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@...osl.org> On Behalf Of
> Mateusz Polchlopek
> Sent: Tuesday, October 22, 2024 1:41 PM
> To: intel-wired-lan@...ts.osuosl.org
> Cc: netdev@...r.kernel.org; Keller, Jacob E <jacob.e.keller@...el.com>; Drewek,
> Wojciech <wojciech.drewek@...el.com>; Sai Krishna
> <saikrishnag@...vell.com>; Simon Horman <horms@...nel.org>; Zaki, Ahmed
> <ahmed.zaki@...el.com>; Polchlopek, Mateusz <mateusz.polchlopek@...el.com>
> Subject: [Intel-wired-lan] [PATCH iwl-next v12 06/14] iavf: add initial framework
> for registering PTP clock
> 
> From: Jacob Keller <jacob.e.keller@...el.com>
> 
> Add the iavf_ptp.c file and fill it in with a skeleton framework to allow registering
> the PTP clock device.
> Add implementation of helper functions to check if a PTP capability is supported
> and handle change in PTP capabilities.
> Enabling virtual clock would be possible, though it would probably perform poorly
> due to the lack of direct time access.
> 
> Signed-off-by: Jacob Keller <jacob.e.keller@...el.com>
> Reviewed-by: Wojciech Drewek <wojciech.drewek@...el.com>
> Reviewed-by: Sai Krishna <saikrishnag@...vell.com>
> Reviewed-by: Simon Horman <horms@...nel.org>
> Co-developed-by: Ahmed Zaki <ahmed.zaki@...el.com>
> Signed-off-by: Ahmed Zaki <ahmed.zaki@...el.com>
> Co-developed-by: Mateusz Polchlopek <mateusz.polchlopek@...el.com>
> Signed-off-by: Mateusz Polchlopek <mateusz.polchlopek@...el.com>


Tested-by: Rafal Romanowski <rafal.romanowski@...el.com>