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 12:15:27 +0200 [thread overview]
Message-ID: <219b7746-fe88-46d5-9a91-5335d202c1d6@enneenne.com> (raw)
In-Reply-To: <80DBB2AF-6C1D-43E2-BB1A-ADABACABE3FE@infradead.org>
> As a parallel thread I'll also look at unconditionally using the
> existing (non-correcting) ktime_get_snapshot_id() so that we have the
> corresponding counter values, and an ioctl for reporting those to
> userspace alongside the ts_real. I am leaning towards using raw counter
> values even when an offset has been applied to the realtime value, but
> still vacillating a bit.
Raw counter values get my vote: userspace set the offset itself with
PPS_SETPARAMS, so it can apply it to the counter if it needs to, while
the counter should stay the value actually read from the hardware. :-)
AFAIK that's also what the kernel consumer gets today: pps_kc_event() is
passed the timestamp before the offset is added, isn't it?
When you get to the ioctl, please post it as an RFC before the code.
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-10-05 10:15 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
2026-10-05 8:49 ` David Woodhouse
2026-10-05 10:15 ` Rodolfo Giometti [this message]
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=219b7746-fe88-46d5-9a91-5335d202c1d6@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®