tick: Assume timekeeping is correctly handed over upon last offline idle call
authorFrederic Weisbecker <frederic@kernel.org>
Sun, 25 Feb 2024 22:55:07 +0000 (23:55 +0100)
committerThomas Gleixner <tglx@linutronix.de>
Mon, 26 Feb 2024 10:37:32 +0000 (11:37 +0100)
commit500f8f9bced86f0c0f2482773bd64a1b7ec9c4e1
tree16c613caa4c0ebacf748c44fee3dcd611b739118
parent3f69d04e146c6e14ccdd4e7b37d93f789229202a
tick: Assume timekeeping is correctly handed over upon last offline idle call

The timekeeping duty is handed over from the outgoing CPU on stop
machine, then the oneshot tick is stopped right after.  Therefore it's
guaranteed that the current CPU isn't the timekeeper upon its last call
to idle.

Besides, calling tick_nohz_idle_stop_tick() while the dying CPU goes
into idle suggests that the tick is going to be stopped while it is
actually stopped already from the appropriate CPU hotplug state.

Remove the confusing call and the obsolete case handling and convert it
to a sanity check that verifies the above assumption.

Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/20240225225508.11587-16-frederic@kernel.org
include/linux/tick.h
kernel/cpu.c
kernel/sched/idle.c
kernel/time/tick-common.c
kernel/time/tick-sched.c