Lines Matching refs:to
8 be loaded to run a torture test. The test periodically outputs
15 It is also possible to specify CONFIG_RCU_TORTURE_TEST=y, which will
17 the CONFIG_RCU_TORTURE_TEST_RUNNABLE config option is used to specify
18 whether the RCU torture tests are to be started immediately during
20 to enable them. This /proc file can be used to repeatedly pause and
24 You will normally -not- want to start the RCU torture tests during boot
40 to force_quiescent_state() within a burst.
43 of calls to force_quiescent_state().
55 irqreader Says to invoke RCU readers from irq level. This is currently
56 done via timers. Defaults to "1" for variants of RCU that
58 -not- permit this know to ignore this variable.)
62 RCU callbacks (and corresponding kthreads) to use for
64 specify this to be non-zero when torture_type indicates a
70 nfakewriters This is the number of RCU fake writer threads to run. Fake
73 torture_type, with a delay between calls to allow for various
75 nfakewriters defaults to 4, which provides enough parallelism
76 to trigger special cases caused by multiple writers, such as
85 The number of seconds between each attempt to execute a
86 randomly selected CPU-hotplug operation. Defaults to
88 kernels, rcutorture will silently refuse to do any
92 onoff_holdoff The number of seconds to wait until starting CPU-hotplug
96 in order to avoid confusing boot-time code with CPUs
100 The number of seconds to keep the test threads affinitied
101 to a particular subset of the CPUs, defaults to 3 seconds.
104 shutdown_secs The number of seconds to run the test before terminating
112 If you need multiple stalls, use modprobe and rmmod to
116 Note that attempts to rmmod rcutorture while the stall
124 The number of seconds to wait after rcutorture starts
125 before stalling a CPU. Defaults to 10 seconds.
130 Setting the interval to zero causes the statistics to
134 stutter The length of time to run the test before pausing for this
135 same period of time. Defaults to "stutter=5", so as
136 to run and pause for (roughly) five-second intervals.
137 Specifying "stutter=0" causes the test to run continuously
140 test_boost Whether or not to test the ability of RCU to do priority
141 boosting. Defaults to "test_boost=1", which performs
148 which can be used to test rcutorture's ability to
153 cycle. Defaults to "test_boost_interval=7". It is
154 usually wise for this value to be relatively prime to
158 The number of seconds to do RCU priority-inversion testing
159 within any given "test_boost_interval". Defaults to
162 test_no_idle_hz Whether or not to test the ability of RCU to operate in
163 a kernel that disables the scheduling-clock interrupt to
164 idle CPUs. Boolean parameter, "1" to test, "0" otherwise.
165 Defaults to omitting this test.
167 torture_type The type of RCU to test, with string values as follows:
178 of RCU in order to help test rcutorture itself.
191 Defaults to "rcu".
208 most systems. On more esoteric configurations, it may be necessary to
209 use other commands to access the output of the printk()s used by
215 automatic determination as to whether RCU operated correctly.
220 to readers.
223 has changed the structure visible to readers.
226 containing structures to be placed into the "rtc" area is empty.
233 failed due to the list being empty. It is not unusual for this
234 to be non-zero, but it is bad for it to be a large fraction of
246 o "rtbke": rcutorture was unable to create the real-time kthreads
247 used to force RCU priority inversion. This value should be zero.
250 used to force RCU priority inversion, it was unable to set them
251 to the real-time priority level of 1. This value should be zero.
254 to resolve RCU priority inversion.
256 o "rtb": The number of times that rcutorture attempted to force
267 And rcutorture prints the error flag string "!!!" to make sure
274 RCU. If you want to see what it looks like when broken, break
281 it is sometimes easier to get the third entry to show up in the
286 should closely correspond to the number of structures allocated,
287 the second to the number that have been removed from reader view,
288 and all but the last remaining to the corresponding number of
301 The "idx" value maps the "old" and "current" values to the underlying
307 The following script may be used to torture RCU:
319 "FAILURE", or "RCU_HOTPLUG" indication to be printk()ed. The first