From: Wen Gu <guwen@linux.alibaba.com>
To: David Woodhouse <dwmw2@infradead.org>, Jakub Kicinski <kuba@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Richard Cochran <richardcochran@gmail.com>,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, xuanzhuo@linux.alibaba.com,
dust.li@linux.alibaba.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v5 1/2] ptp: introduce Alibaba CIPU PHC driver
Date: Mon, 12 Jan 2026 11:45:37 +0800 [thread overview]
Message-ID: <028dc6e9-c15a-4258-b72f-a4efe95503cc@linux.alibaba.com> (raw)
In-Reply-To: <de8952121036deb58c07be294a044b5ff5bc00f4.camel@infradead.org>
On 2026/1/9 17:25, David Woodhouse wrote:
> On Sun, 2026-01-04 at 14:11 +0800, Wen Gu wrote:
>>
>> IIUC, the main block is that you don't want to maintain these pure
>> phc clocks, as you mentioned in [3]. I agree with this as well. So I
>> propose to group these pure phc drivers together (e.g. drivers/phc)
>> and move them from the network maintenance domain to the clock maintenance
>> domain.
>
> I think that makes sense. These clocks can still be registered as PTP
> clocks because that's one of the most sensible interfaces to userspace,
> but the implementations can live elsewhere outside the networking
> maintenance domain.
>
Yes. The PTP interface has become a common choice for exposing these
clocks to userspace, and it is not limited to NIC-based implementations.
I have posted an RFC to reach a consensus on organizing these clocks:
https://lore.kernel.org/netdev/0afe19db-9c7f-4228-9fc2-f7b34c4bc227@linux.alibaba.com/
> In a lot of cases we'd want to use them for RTC too, so that the
> kernel's CLOCK_REALTIME can be initialised from them. And especially
> for microvms I'd like to *synchronize* the kernel's clock from them
> automatically too.
>
This is also a good use-case that supports having these clocks available.
Regards.
next prev parent reply other threads:[~2026-01-12 3:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 12:13 [PATCH net-next v5 0/2] ptp: Alibaba CIPU PTP clock driver Wen Gu
2025-10-30 12:13 ` [PATCH net-next v5 1/2] ptp: introduce Alibaba CIPU PHC driver Wen Gu
2025-10-31 23:58 ` Jakub Kicinski
2025-11-05 10:22 ` Wen Gu
2025-11-06 0:24 ` Jakub Kicinski
2025-11-27 5:48 ` Wen Gu
2025-11-27 16:36 ` Jakub Kicinski
2025-11-28 6:22 ` Wen Gu
2025-11-28 18:24 ` Jakub Kicinski
2025-12-01 6:04 ` Wen Gu
2025-12-12 6:50 ` Wen Gu
2025-12-12 22:50 ` Jakub Kicinski
2025-12-14 14:03 ` Wen Gu
2025-12-16 21:58 ` Jakub Kicinski
2025-12-17 12:40 ` Wen Gu
2025-12-22 7:18 ` Wen Gu
2026-01-02 19:51 ` Jakub Kicinski
2026-01-04 6:11 ` Wen Gu
2026-01-09 9:25 ` David Woodhouse
2026-01-12 3:45 ` Wen Gu [this message]
2025-12-18 12:28 ` David Woodhouse
2025-12-22 12:44 ` Wen Gu
2025-10-30 12:13 ` [PATCH net-next v5 2/2] ptp: add sysfs documentation for " Wen Gu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=028dc6e9-c15a-4258-b72f-a4efe95503cc@linux.alibaba.com \
--to=guwen@linux.alibaba.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=dwmw2@infradead.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.de \
--cc=xuanzhuo@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox