!3066 rcu: Add RCU stall diagnosis information

Merge Pull Request from: @ci-robot 
 
PR sync from: Zhen Lei <thunder.leizhen@huawei.com>
https://mailweb.openeuler.org/hyperkitty/list/kernel@openeuler.org/message/P6C4E4WHUS76SMDAU4NM6HFAKILY7H7P/ 
v2 --> v3:
Add "# CONFIG_RCU_CPU_STALL_CPUTIME is not set" into openeuler_defconfig.

v1 --> v2:
Remove patch 1 in v1: rcu: Prevent lockdep-RCU splats on lock acquisition/release
It had arleady been merged.

v1:
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 (2):
  rcu: For RCU grace-period kthread starvation, dump last CPU it ran on
  rcu: Do not NMI offline CPUs

Zhen Lei (7):
  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
  config: update openeuler_defconfig for arm64 and x86


-- 
2.25.1
 
https://gitee.com/openeuler/kernel/issues/I7OIXK 
 
Link:https://gitee.com/openeuler/kernel/pulls/3066

 

Reviewed-by: Zucheng Zheng <zhengzucheng@huawei.com>
Reviewed-by: Wei Li <liwei391@huawei.com>
Reviewed-by: Liu Chao <liuchao173@huawei.com>
Signed-off-by: Jialin Zhang <zhangjialin11@huawei.com>