From: Thomas Gleixner <tglx@linutronix.de>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org, Wanpeng Li <wanpeng.li@hotmail.com>
Subject: Re: [PATCH] nohz: fix jiffies warp while switch to low-res nohz mode
Date: Tue, 26 Jan 2016 16:21:01 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1601261615190.3886@nanos> (raw)
In-Reply-To: <1453344859-5235-1-git-send-email-wanpeng.li@hotmail.com>
On Thu, 21 Jan 2016, Wanpeng Li wrote:
> After commit 0ff53d096422 ("tick: sched: Force tick interrupt and get rid
> of softirq magic"), next expire time is overwritten by last_jiffies_update
> while switch to low-res nohz mode which leads to jiffies warp. This patch
> fix it by programming ce device the expire time in the future.
> - hrtimer_forward_now(&ts->sched_timer, tick_period);
> hrtimer_set_expires(&ts->sched_timer, next);
> - tick_program_event(next, 1);
> + hrtimer_forward_now(&ts->sched_timer, tick_period);
> + tick_program_event(hrtimer_get_expires(&ts->sched_timer), 1);
> tick_nohz_activate(ts, NOHZ_MODE_LOWRES);
I agree, that the ordering forward/set is wrong and needs to be fixed, but how
does that result in a jiffies warp?
tick_nohz_handler()
tick_sched_do_timer()
tick_do_update_jiffies64()
delta = ktime_sub(now, last_jiffies_update);
if (delta.tv64 < tick_period.tv64)
return;
So if that timer fires early, tick_do_update_jiffies64() will just return and
do nothing. So what makes jiffies warp?
Unless I'm missing something, this changelog is patently wrong.
Thanks,
tglx
next prev parent reply other threads:[~2016-01-26 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 2:54 Wanpeng Li
2016-01-26 15:21 ` Thomas Gleixner [this message]
2016-01-27 11:31 ` Wanpeng Li
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.11.1601261615190.3886@nanos \
--to=tglx@linutronix.de \
--cc=fweisbec@gmail.com \
--cc=kernellwp@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=wanpeng.li@hotmail.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®