Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.21.1806222308560.1589@nanos.tec.linutronix.de>
References: <20180604133421.19559-1-mlichvar@redhat.com> <alpine.DEB.2.21.1806222308560.1589@nanos.tec.linutronix.de>
From:   John Stultz <john.stultz@linaro.org>
Date:   Fri, 22 Jun 2018 14:12:28 -0700
Message-ID: <CALAqxLUh+A1nJF1n2G_pRPrUQPMD6b-9fAdojPmAOkmnUM+-Nw@mail.gmail.com>
Subject: Re: [PATCHv2] timekeeping: Update multiplier when NTP frequency is
 set directly
To:     Thomas Gleixner <tglx@linutronix.de>
Cc:     Miroslav Lichvar <mlichvar@redhat.com>,
        lkml <linux-kernel@vger.kernel.org>,
        Richard Cochran <richardcochran@gmail.com>,
        Prarit Bhargava <prarit@redhat.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.

thanks
-john