netdev - Re: [RFC PATCH v2] net: add net-device TX clock source selection framework

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: <20250905160333.715c34ac@kernel.org>
Date: Fri, 5 Sep 2025 16:03:33 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: "Kubalewski, Arkadiusz" <arkadiusz.kubalewski@...el.com>
Cc: "Nguyen, Anthony L" <anthony.l.nguyen@...el.com>, "Kitszel, Przemyslaw"
 <przemyslaw.kitszel@...el.com>, "andrew+netdev@...n.ch"
 <andrew+netdev@...n.ch>, "davem@...emloft.net" <davem@...emloft.net>,
 "edumazet@...gle.com" <edumazet@...gle.com>, "pabeni@...hat.com"
 <pabeni@...hat.com>, "horms@...nel.org" <horms@...nel.org>,
 "sdf@...ichev.me" <sdf@...ichev.me>, "almasrymina@...gle.com"
 <almasrymina@...gle.com>, "asml.silence@...il.com"
 <asml.silence@...il.com>, "leitao@...ian.org" <leitao@...ian.org>,
 "kuniyu@...gle.com" <kuniyu@...gle.com>, "jiri@...nulli.us"
 <jiri@...nulli.us>, "Loktionov, Aleksandr" <aleksandr.loktionov@...el.com>,
 "Vecera, Ivan" <ivecera@...hat.com>, "linux-kernel@...r.kernel.org"
 <linux-kernel@...r.kernel.org>, "intel-wired-lan@...ts.osuosl.org"
 <intel-wired-lan@...ts.osuosl.org>, "netdev@...r.kernel.org"
 <netdev@...r.kernel.org>
Subject: Re: [RFC PATCH v2] net: add net-device TX clock source selection
 framework

On Fri, 5 Sep 2025 11:14:09 +0000 Kubalewski, Arkadiusz wrote:
> Please share your thoughts, right now I see two ways forward:
> - moving netdev netlink to rt-netlink,
> - kind of hacking into dpll subsystem with 'ext-ref' and output netdev pin.

I haven't spend much time thinking this thru, but my intuition would be
similar to what we have. One dpll pin exposed via rtnetlink (like Ivan
shows in his reply), and then the selection of input for that pin kinda
looks like the mux problem that we already solved with the DPLL API?
IOW I guess "hacking into dpll subsystem" would be my first choice?