aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/rcutorture/bin
diff options
context:
space:
mode:
authorSangmoon Kim <sangmoon.kim@samsung.com>2021-03-02 20:55:15 +0900
committerPaul E. McKenney <paulmck@kernel.org>2021-03-15 13:53:24 -0700
commit565cfb9e64dac1aadf7e2130fcda19a1c018df66 (patch)
tree07a85851e876c0cb1b270e51f6677c5fa9e44180 /tools/testing/selftests/rcutorture/bin
parentrcu: Add explicit barrier() to __rcu_read_unlock() (diff)
downloadlinux-dev-565cfb9e64dac1aadf7e2130fcda19a1c018df66.tar.xz
linux-dev-565cfb9e64dac1aadf7e2130fcda19a1c018df66.zip
rcu/tree: Add a trace event for RCU CPU stall warnings
This commit adds a trace event which allows tracing the beginnings of RCU CPU stall warnings on systems where sysctl_panic_on_rcu_stall is disabled. The first parameter is the name of RCU flavor like other trace events. The second parameter indicates whether this is a stall of an expedited grace period, a self-detected stall of a normal grace period, or a stall of a normal grace period detected by some CPU other than the one that is stalled. RCU CPU stall warnings are often caused by external-to-RCU issues, for example, in interrupt handling or task scheduling. Therefore, this event uses TRACE_EVENT, not TRACE_EVENT_RCU, to avoid requiring those interested in tracing RCU CPU stalls to rebuild their kernels with CONFIG_RCU_TRACE=y. Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com> Reviewed-by: Neeraj Upadhyay <neeraju@codeaurora.org> Signed-off-by: Sangmoon Kim <sangmoon.kim@samsung.com> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'tools/testing/selftests/rcutorture/bin')
0 files changed, 0 insertions, 0 deletions