mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	Ryan Luu <rluu@amazon.com>, Julien Ridoux <ridouxj@amazon.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] [DO NOT MERGE] timekeeping: Apply extrapolated ntp_error to clock snapshots
Date: Mon, 5 Oct 2026 10:15:01 +0200	[thread overview]
Message-ID: <f432aee3-9bda-430c-9cb6-e35248c87b3d@enneenne.com> (raw)
In-Reply-To: <46df3bedea175007a6480b4cb8ba070c6ff3d527.camel@infradead.org>

On 03/10/2026 00:47, David Woodhouse wrote:
> On Fri, 2026-10-02 at 12:26 +0200, Rodolfo Giometti wrote:
>>  
>>> So I think we do need it, and my inclination is to hold off on enabling
>>> CONFIG_NTP_PPS for tickless kernels until we do. But I'll defer to your
>>> preference. If you want to merge it sooner on the basis that with a
>>> 1PPS signal the system doesn't get to sleep for long *anyway*, I can do
>>> another test run with just patches 1-4.
>>>
>>
>> Yes, please do that run. This patch changes what PPS_FETCH returns to
>> userspace, so it has to wait for the chrony and ntpd people anyway; if
>> 1-4 alone are good enough at 1PPS I'd rather not tie the tickless
>> enablement to it.
> 
> https://david.woodhou.se/ntptest-r64/rodolfo-14-tickless-1hz/
> 
> Fairly much identical to the full series running tickless, which was
> https://david.woodhou.se/ntptest-r64/tickless-1hz/
> 
> And not really much worse than the tickful variant
> https://david.woodhou.se/ntptest-r64/tickful-1hz/
> 
> The ntp_error isn't measured because it's the clean series and most of
> the instrumentation is gone. I'll set the 5s pulse version running
> overnight.
> 
> The series is also tested on four virtual machines on the same host,
> tickful and tickless, patches vs. baseline. You can see the tickless
> baseline wobble when the actual frequency changes, while the other
> three remain stable. You can also see ntp_error on both baseline
> kernels spiking during the initial sync.
> https://david.woodhou.se/ntptest-virt/

Thanks, that's convincing: with 1-4 alone tickless at 1Hz looks the
same as with the full series, so I'm fine with the tickless enablement
not depending on this patch. :-)

Please put these numbers, and the 5s ones when you have them, in the commit
message of the patch dropping !NO_HZ_COMMON.

Ciao,

Rodolfo

-- 
GNU/Linux Solutions                  e-mail: giometti@enneenne.com
Linux Device Driver                          giometti@linux.it
Embedded Systems                     phone:  +39 349 2432127
UNIX programming

  reply	other threads:[~2026-10-05  8:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 20:21 [PATCH 0/5] timekeeping: Reduce magnitude of ntp_error David Woodhouse
2026-10-01 20:21 ` [PATCH 1/5] timekeeping: Allow tick_length changes to apply mid-tick David Woodhouse
2026-10-01 20:21 ` [PATCH 2/5] ntp: Recalculate skew_delta when the phase offset changes David Woodhouse
2026-10-01 20:21 ` [PATCH 3/5] timekeeping: Bound idle sleep while a phase slew is in flight David Woodhouse
2026-10-01 20:21 ` [PATCH 4/5] timekeeping: Reinstate proportional correction of ntp_error David Woodhouse
2026-10-05 10:04   ` Miroslav Lichvar
2026-10-05 13:17     ` David Woodhouse
2026-10-01 20:21 ` [PATCH 5/5] [DO NOT MERGE] timekeeping: Apply extrapolated ntp_error to clock snapshots David Woodhouse
2026-10-02  8:30   ` Rodolfo Giometti
2026-10-02  9:14     ` David Woodhouse
2026-10-02 10:26       ` Rodolfo Giometti
2026-10-02 22:47         ` David Woodhouse
2026-10-05  8:15           ` Rodolfo Giometti [this message]
2026-10-05  8:49             ` David Woodhouse
2026-10-05 10:15               ` Rodolfo Giometti
2026-10-05 10:49                 ` 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=f432aee3-9bda-430c-9cb6-e35248c87b3d@enneenne.com \
    --to=giometti@enneenne.com \
    --cc=dwmw2@infradead.org \
    --cc=jstultz@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlichvar@redhat.com \
    --cc=ridouxj@amazon.com \
    --cc=rluu@amazon.com \
    --cc=sboyd@kernel.org \
    --cc=tglx@kernel.org \
    /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®