From: Jakub Kicinski <kuba@kernel.org>
To: Wen Gu <guwen@linux.alibaba.com>
Cc: 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: Wed, 5 Nov 2025 16:24:29 -0800 [thread overview]
Message-ID: <20251105162429.37127978@kernel.org> (raw)
In-Reply-To: <8a74f801-1de5-4a1d-adc7-66a91221485d@linux.alibaba.com>
On Wed, 5 Nov 2025 18:22:19 +0800 Wen Gu wrote:
> On 2025/11/1 07:58, Jakub Kicinski wrote:
> > On Thu, 30 Oct 2025 20:13:13 +0800 Wen Gu wrote:
> >> This adds a driver for Alibaba CIPU PTP clock. The CIPU, an underlying
> >> infrastructure of Alibaba Cloud, synchronizes time with atomic clocks
> >> via the network and provides microsecond or sub-microsecond precision
> >> timestamps for VMs and bare metals on cloud.
> >>
> >> User space processes, such as chrony, running in VMs or on bare metals
> >> can get the high precision time through the PTP device exposed by this
> >> driver.
> >
> > As mentioned on previous revisions this is a pure clock device which has
> > nothing to do with networking and PTP.
>
> I don't quite agree that this has nothing to do with PTP.
>
> What is the difference between this CIPU PTP driver and other PTP drivers
> under drivers/ptp? such as ptp_s390, ptp_vmw, ptp_pch, and others. Most of
> these PTP drivers do not directly involve IEEE 1588 or networking as well.
We can't delete existing drivers. It used to be far less annoying
until every cloud vendor under the sun decided to hack up their own
implementation of something as simple as the clock.
> > There should be a separate class
> > for "hypervisor clocks", if not a common driver.
>
> 'hypervisor clock' is not very accurate. CIPU PTP can be used in VM and
> bare metal scenarios, and bare metals do not need hypervisors.
I know.
next prev parent reply other threads:[~2025-11-06 0:24 UTC|newest]
Thread overview: 19+ 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 [this message]
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
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=20251105162429.37127978@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).