2 # RCU-related debugging configuration options
15 tristate "performance tests for RCU"
16 depends on DEBUG_KERNEL
22 This option provides a kernel module that runs performance
23 tests on the RCU infrastructure. The kernel module may be built
24 after the fact on the running kernel to be tested, if desired.
26 Say Y here if you want RCU performance tests to be built into
28 Say M if you want the RCU performance tests to build as a module.
29 Say N if you are unsure.
31 config RCU_TORTURE_TEST
32 tristate "torture tests for RCU"
33 depends on DEBUG_KERNEL
39 This option provides a kernel module that runs torture tests
40 on the RCU infrastructure. The kernel module may be built
41 after the fact on the running kernel to be tested, if desired.
43 Say Y here if you want RCU torture tests to be built into
45 Say M if you want the RCU torture tests to build as a module.
46 Say N if you are unsure.
48 config RCU_CPU_STALL_TIMEOUT
49 int "RCU CPU stall timeout in seconds"
50 depends on RCU_STALL_COMMON
54 If a given RCU grace period extends more than the specified
55 number of seconds, a CPU stall warning is printed. If the
56 RCU grace period persists, additional CPU stall warnings are
57 printed at more widely spaced intervals.
60 bool "Enable tracing for RCU"
61 depends on DEBUG_KERNEL
65 This option enables additional tracepoints for ftrace-style
68 Say Y here if you want to enable RCU tracing
69 Say N if you are unsure.
72 bool "Provide debugging asserts for adding NO_HZ support to an arch"
73 depends on DEBUG_KERNEL
75 This option provides consistency checks in RCU's handling of
76 NO_HZ. These checks have proven quite helpful in detecting
77 bugs in arch-specific NO_HZ code.
79 Say N here if you need ultimate kernel/user switch latencies
80 Say Y if you are unsure
82 endmenu # "RCU Debugging"