clockevents: prevent stale tick_next_period for onlining CPUs
Impact: possible hang on CPU onlining in timer one shot mode. The tick_next_period variable is only used during boot on nohz/highres enabled systems, but for CPU onlining it needs to be maintained when the per cpu clock events device operates in one shot mode. Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
This commit is contained in:
parent
4faac97d44
commit
49d670fb8d
1 changed files with 3 additions and 0 deletions
|
@ -75,6 +75,9 @@ static void tick_do_update_jiffies64(ktime_t now)
|
||||||
incr * ticks);
|
incr * ticks);
|
||||||
}
|
}
|
||||||
do_timer(++ticks);
|
do_timer(++ticks);
|
||||||
|
|
||||||
|
/* Keep the tick_next_period variable up to date */
|
||||||
|
tick_next_period = ktime_add(last_jiffies_update, tick_period);
|
||||||
}
|
}
|
||||||
write_sequnlock(&xtime_lock);
|
write_sequnlock(&xtime_lock);
|
||||||
}
|
}
|
||||||
|
|
Loading…
Add table
Reference in a new issue