tick/rcu: Stop allowing RCU_SOFTIRQ in idle
authorFrederic Weisbecker <frederic@kernel.org>
Tue, 8 Feb 2022 16:16:34 +0000 (17:16 +0100)
committerPaul E. McKenney <paulmck@kernel.org>
Mon, 14 Feb 2022 18:51:07 +0000 (10:51 -0800)
commit4569212dbab7509b3589e2adda467aa99cb5e2b6
tree1f21ce41123427e3b535283858e3641fb6b11cd5
parent273f1176acfb036dbc1cc0f5d42f40701c735ebe
tick/rcu: Stop allowing RCU_SOFTIRQ in idle

RCU_SOFTIRQ used to be special in that it could be raised on purpose
within the idle path to prevent from stopping the tick. Some code still
prevents from unnecessary warnings related to this specific behaviour
while entering in dynticks-idle mode.

However the nohz layout has changed quite a bit in ten years, and the
removal of CONFIG_RCU_FAST_NO_HZ has been the final straw to this
safe-conduct. Now the RCU_SOFTIRQ vector is expected to be raised from
sane places.

A remaining corner case is admitted though when the vector is invoked
in fragile hotplug path.

Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>
Tested-by: Paul Menzel <pmenzel@molgen.mpg.de>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
include/linux/interrupt.h
kernel/time/tick-sched.c