APPLIED: [J] [SRU][J:linux-bluefield][PATCH 0/1] Stop allowing RCU_SOFTIRQ in idle

[Tim Gardner]

On 12/8/22 4:52 PM, Bodong Wang wrote:
> 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.
> 
> This patch is applicable for both J and F.
> 
> Frederic Weisbecker (1):
>    tick/rcu: Stop allowing RCU_SOFTIRQ in idle
> 
>   include/linux/interrupt.h |  8 ++++++-
>   kernel/time/tick-sched.c  | 50 +++++++++++++++++++++++++++++++--------
>   2 files changed, 47 insertions(+), 11 deletions(-)
> 
Applied to jammy/linux-bluefield:master-next. Thanks.

In light of Bodong's comments regarding the Focal patch I've reverted 
'tick/rcu: Stop allowing RCU_SOFTIRQ in idle' and pushed the revert to 
Focal linux-bluefield/master-next. The cranker can decide to just drop 
the series since the original patch has not been released.

-rtg
-- 
-----------
Tim Gardner
Canonical, Inc