mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Miroslav Lichvar <mlichvar@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	John Stultz <john.stultz@linaro.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:09:20 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1806222308560.1589@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20180604133421.19559-1-mlichvar@redhat.com>

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 ?????

> 
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: John Stultz <john.stultz@linaro.org>
> Cc: Richard Cochran <richardcochran@gmail.com>
> Cc: Prarit Bhargava <prarit@redhat.com>
> Signed-off-by: Miroslav Lichvar <mlichvar@redhat.com>
> ---
> 
> Notes:
>     RFC->v1:
>     - added a new parameter to force the update of the timekeeper to the current
>       NTP tick length only from adjtimex()
>     - added timekeeping_advance() to keep the parameter local to timekeeping.c
>     v1->v2:
>     - replaced bool parameter with enum
>     - changed timekeeping_advance() to not make any updates for TK_ADV_FREQ with
>       !ARCH_USES_GETTIMEOFFSET (an alternative might be to update with zero offset)
> 
>  kernel/time/timekeeping.c | 36 ++++++++++++++++++++++++++++++------
>  1 file changed, 30 insertions(+), 6 deletions(-)
> 
> diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
> index 49cbceef5deb..a08ef3771ab5 100644
> --- a/kernel/time/timekeeping.c
> +++ b/kernel/time/timekeeping.c
> @@ -34,6 +34,14 @@
>  #define TK_MIRROR		(1 << 1)
>  #define TK_CLOCK_WAS_SET	(1 << 2)
>  
> +enum timekeeping_adv_mode {
> +	/* Update timekeeper when a tick has passed */
> +	TK_ADV_TICK,
> +
> +	/* Update timekeeper on a direct frequency change */
> +	TK_ADV_FREQ
> +};
> +
>  /*
>   * The most important data for readout fits into a single 64 byte
>   * cache line.
> @@ -2021,11 +2029,11 @@ static u64 logarithmic_accumulation(struct timekeeper *tk, u64 offset,
>  	return offset;
>  }
>  
> -/**
> - * update_wall_time - Uses the current clocksource to increment the wall time
> - *
> +/*
> + * timekeeping_advance - Updates the timekeeper to the current time and
> + * current NTP tick length
>   */
> -void update_wall_time(void)
> +static void timekeeping_advance(enum timekeeping_adv_mode mode)
>  {
>  	struct timekeeper *real_tk = &tk_core.timekeeper;
>  	struct timekeeper *tk = &shadow_timekeeper;
> @@ -2042,14 +2050,17 @@ void update_wall_time(void)
>  
>  #ifdef CONFIG_ARCH_USES_GETTIMEOFFSET
>  	offset = real_tk->cycle_interval;
> +
> +	if (mode != TK_ADV_TICK)
> +		goto out;
>  #else
>  	offset = clocksource_delta(tk_clock_read(&tk->tkr_mono),
>  				   tk->tkr_mono.cycle_last, tk->tkr_mono.mask);
> -#endif
>  
>  	/* Check if there's really nothing to do */
> -	if (offset < real_tk->cycle_interval)
> +	if (offset < real_tk->cycle_interval && mode == TK_ADV_TICK)
>  		goto out;
> +#endif
>  
>  	/* Do some additional sanity checking */
>  	timekeeping_check_update(tk, offset);
> @@ -2105,6 +2116,15 @@ void update_wall_time(void)
>  		clock_was_set_delayed();
>  }
>  
> +/**
> + * update_wall_time - Uses the current clocksource to increment the wall time
> + *
> + */
> +void update_wall_time(void)
> +{
> +	timekeeping_advance(TK_ADV_TICK);
> +}
> +
>  /**
>   * getboottime64 - Return the real time of system boot.
>   * @ts:		pointer to the timespec64 to be set
> @@ -2332,6 +2352,10 @@ int do_adjtimex(struct timex *txc)
>  	write_seqcount_end(&tk_core.seq);
>  	raw_spin_unlock_irqrestore(&timekeeper_lock, flags);
>  
> +	/* Update the multiplier immediately if frequency was set directly */
> +	if (txc->modes & (ADJ_FREQUENCY | ADJ_TICK))
> +		timekeeping_advance(TK_ADV_FREQ);
> +
>  	if (tai != orig_tai)
>  		clock_was_set();
>  
> -- 
> 2.14.3
> 
> 

  reply	other threads:[~2018-06-22 21:09 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 [this message]
2018-06-22 21:12   ` John Stultz
2018-06-22 21:28     ` Thomas Gleixner

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.1806222308560.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®