tick/nohz: Set the correct expiry when switching to nohz/lowres mode
commitd024d46ec5203664fac872a20f7d75125db952da
authorWanpeng Li <kernellwp@gmail.com>
Wed, 27 Jan 2016 11:26:07 +0000 (27 19:26 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 3 Mar 2016 23:07:26 +0000 (3 15:07 -0800)
tree3a404afc1df8362f1eb2d6a6c1aee85df6f3931d
parente43193617315070ca9a6ca55794760e328fe4e9b
tick/nohz: Set the correct expiry when switching to nohz/lowres mode

commit 1ca8ec532fc2d986f1f4a319857bb18e0c9739b4 upstream.

commit 0ff53d096422 sets the next tick interrupt to the last jiffies update,
i.e. in the past, because the forward operation is invoked before the set
operation. There is no resulting damage (yet), but we get an extra pointless
tick interrupt.

Revert the order so we get the next tick interrupt in the future.

Fixes: commit 0ff53d096422 "tick: sched: Force tick interrupt and get rid of softirq magic"
Signed-off-by: Wanpeng Li <wanpeng.li@hotmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Link: http://lkml.kernel.org/r/1453893967-3458-1-git-send-email-wanpeng.li@hotmail.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
kernel/time/tick-sched.c