tick/sched: Remove bogus boot "safety" check
authorThomas Gleixner <tglx@linutronix.de>
Sun, 6 Dec 2020 21:12:55 +0000 (22:12 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 6 Jan 2021 13:48:40 +0000 (14:48 +0100)
commit480abac78e032d83a5797e39947526e94e7c8427
tree8fad07e900baee2afcafa8f0425a62540625036f
parent1dab82dd202d27ad4266e2711e250bfe5127bcbf
tick/sched: Remove bogus boot "safety" check

[ Upstream commit ba8ea8e7dd6e1662e34e730eadfc52aa6816f9dd ]

can_stop_idle_tick() checks whether the do_timer() duty has been taken over
by a CPU on boot. That's silly because the boot CPU always takes over with
the initial clockevent device.

But even if no CPU would have installed a clockevent and taken over the
duty then the question whether the tick on the current CPU can be stopped
or not is moot. In that case the current CPU would have no clockevent
either, so there would be nothing to keep ticking.

Remove it.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Frederic Weisbecker <frederic@kernel.org>
Link: https://lore.kernel.org/r/20201206212002.725238293@linutronix.de
Signed-off-by: Sasha Levin <sashal@kernel.org>
kernel/time/tick-sched.c