From: Thomas Gleixner <tglx@linutronix.de>
To: John Stultz <john.stultz@linaro.org>
Cc: Miroslav Lichvar <mlichvar@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
Richard Cochran <richardcochran@gmail.com>,
Prarit Bhargava <prarit@redhat.com>
Subject: Re: [PATCHv2] timekeeping: Update multiplier when NTP frequency is set directly
Date: Fri, 22 Jun 2018 23:28:10 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1806222327341.1589@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CALAqxLUh+A1nJF1n2G_pRPrUQPMD6b-9fAdojPmAOkmnUM+-Nw@mail.gmail.com>
On Fri, 22 Jun 2018, John Stultz wrote:
> On Fri, Jun 22, 2018 at 2:09 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> > On Mon, 4 Jun 2018, Miroslav Lichvar wrote:
> >
> >> When the NTP frequency is set directly from userspace using the
> >> ADJ_FREQUENCY or ADJ_TICK timex mode, immediately update the
> >> timekeeper's multiplier instead of waiting for the next tick.
> >>
> >> This removes a hidden non-deterministic delay in setting of the
> >> frequency and allows an extremely tight control of the system clock
> >> with update rates close to or even exceeding the kernel HZ.
> >>
> >> The update is limited to archs using modern timekeeping
> >> (!ARCH_USES_GETTIMEOFFSET).
> >
> > John ?????
>
> Yea. I've got this in my toqueue list. I'm going to take another pass
> at testing and hopefully send it your way.
No hurry. I just wanted to make sure that it didn't fall through the
cracks.
Thanks,
tglx
prev parent reply other threads:[~2018-06-22 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 13:34 Miroslav Lichvar
2018-06-22 21:09 ` Thomas Gleixner
2018-06-22 21:12 ` John Stultz
2018-06-22 21:28 ` Thomas Gleixner [this message]
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=alpine.DEB.2.21.1806222327341.1589@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlichvar@redhat.com \
--cc=prarit@redhat.com \
--cc=richardcochran@gmail.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®