nohz: Reset next_tick cache even when the timer has no regs
Handle tick interrupts whose regs are NULL, out of general paranoia. It happens when hrtimer_interrupt() is called from non-interrupt contexts, such as hotplug CPU down events. Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: linux-kernel@vger.kernel.org Signed-off-by: Ingo Molnar <mingo@kernel.org>
This commit is contained in:
parent
411fe24e6b
commit
7c25904508
1 changed files with 2 additions and 0 deletions
|
@ -1202,6 +1202,8 @@ static enum hrtimer_restart tick_sched_timer(struct hrtimer *timer)
|
|||
*/
|
||||
if (regs)
|
||||
tick_sched_handle(ts, regs);
|
||||
else
|
||||
ts->next_tick = 0;
|
||||
|
||||
/* No need to reprogram if we are in idle or full dynticks mode */
|
||||
if (unlikely(ts->tick_stopped))
|
||||
|
|
Loading…
Reference in a new issue