PR sync from: Zhen Lei thunder.leizhen@huawei.com
https://mailweb.openeuler.org/hyperkitty/list/kernel@openeuler.org/message/SOFSM4XQUKK6ZI2SHRK4VAAE4K3ZNO75/
In some extreme cases, such as the I/O pressure test, the CPU usage may
be 100%, causing RCU stall. In this case, the printed information about
current is not useful. Displays the number and usage of hard interrupts,
soft interrupts, and context switches that are generated within half of
the CPU stall timeout, can help us make a general judgment. In other
cases, we can preliminarily determine whether an infinite loop occurs
when local_irq, local_bh or preempt is disabled.

Neeraj Upadhyay (1):
rcu: Check and report missed fqs timer wakeup on RCU stall

Paul E. McKenney (3):
rcu: Prevent lockdep-RCU splats on lock acquisition/release
rcu: For RCU grace-period kthread starvation, dump last CPU it ran on
rcu: Do not NMI offline CPUs

Zhen Lei (6):
sched/debug: Try trigger_single_cpu_backtrace(cpu) in dump_cpu_task()
sched/debug: Show the registers of 'current' in dump_cpu_task()
sched: Add helper kstat_cpu_softirqs_sum()
sched: Add helper nr_context_switches_cpu()
rcu: Add RCU stall diagnosis information
rcu: Align the output of RCU CPU stall warning messages

--
2.34.1

#I7OIXK:回合主线的RCU stall维测增强补丁
#I6AVM6:5.10.160-5.10.163 LTS补丁回合