From: Rodolfo Giometti <giometti@enneenne.com>
To: David Woodhouse <dwmw2@infradead.org>,
Thomas Gleixner <tglx@kernel.org>,
John Stultz <jstultz@google.com>
Cc: Stephen Boyd <sboyd@kernel.org>,
Miroslav Lichvar <mlichvar@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
Jie Wang <jie.wang@intel.com>, Yuan Wang <yuan1.wang@intel.com>,
Ryan Luu <rluu@amazon.com>, Julien Ridoux <ridouxj@amazon.com>,
linux-kernel@vger.kernel.org, nh-open-source@amazon.com
Subject: Re: [PATCH v2 0/6] timekeeping: Reduce magnitude of ntp_error
Date: Fri, 6 Nov 2026 09:44:50 +0100 [thread overview]
Message-ID: <fd554169-8870-40d9-83a7-fdcd838aaa8e@enneenne.com> (raw)
In-Reply-To: <a5c57e49001c9777d8b6fdce71ffa743004908c9.camel@infradead.org>
On 06/11/2026 04:24, David Woodhouse wrote:
> I think I reordered and reworded things as agreed with Rodolfo; please
> shout if I screwed something up. What's sitting behind this in
> https://git.infradead.org/users/dwmw2/linux.git/shortlog/refs/heads/ffclock
> is the timekeeping reference stuff for importing/exporting vmclock, and
> preserving timekeeping across KHO:
No, the 5/6 and 6/6 split is what we agreed, thanks. On 6/6 I'm still
missing the ntpd side, see my reply there.
>
> The !NO_HZ_COMMON dependency can sit around for a little while longer
> until the series above is actually applied, and it can note the
> actually commit ID of its dependencies (which I think we agreed is just
> patches 1 & 2 of the series above). I'll probably round it up with the
> other PPS stuff I haven't quite got publishable yet, improving the
> filtering and then working on counter-based capture and UAPI.
AFAIK we agreed on patches 1-4: the tickless run you did for me
(rodolfo-14-tickless-1hz) had all four applied. If 1 and 2 alone are
enough, could you put numbers for that in the commit message too?
And for the UAPI, an RFC first please. :-)
Ciao,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti@enneenne.com
Linux Device Driver giometti@linux.it
Embedded Systems phone: +39 349 2432127
UNIX programming
next prev parent reply other threads:[~2026-11-06 8:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 3:08 David Woodhouse
2026-11-06 3:08 ` [PATCH v2 1/6] timekeeping: Allow tick_length changes to apply mid-tick David Woodhouse
2026-11-06 3:08 ` [PATCH v2 2/6] ntp: Recalculate skew_delta when the phase offset changes David Woodhouse
2026-11-06 3:08 ` [PATCH v2 3/6] timekeeping: Bound idle sleep while a phase slew is in flight David Woodhouse
2026-11-06 3:08 ` [PATCH v2 4/6] timekeeping: Reinstate proportional correction of ntp_error David Woodhouse
2026-11-06 3:08 ` [PATCH v2 5/6] pps: Always use ktime_get_snapshot_id() for pps_get_ts() David Woodhouse
2026-11-06 8:44 ` Rodolfo Giometti
2026-11-06 3:08 ` [PATCH v2 6/6] timekeeping: Apply extrapolated ntp_error to clock snapshots David Woodhouse
2026-11-06 8:44 ` Rodolfo Giometti
2026-11-06 3:24 ` [PATCH v2 0/6] timekeeping: Reduce magnitude of ntp_error David Woodhouse
2026-11-06 8:44 ` Rodolfo Giometti [this message]
2026-11-06 18:05 ` David Woodhouse
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=fd554169-8870-40d9-83a7-fdcd838aaa8e@enneenne.com \
--to=giometti@enneenne.com \
--cc=dwmw2@infradead.org \
--cc=jie.wang@intel.com \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mlichvar@redhat.com \
--cc=nh-open-source@amazon.com \
--cc=richardcochran@gmail.com \
--cc=ridouxj@amazon.com \
--cc=rluu@amazon.com \
--cc=sboyd@kernel.org \
--cc=tglx@kernel.org \
--cc=yuan1.wang@intel.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
all inboxes | Powered by JetHome®