aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@us.ibm.com>2006-06-27 05:54:02 -0400
committerLinus Torvalds <torvalds@g5.osdl.org>2006-06-27 20:32:40 -0400
commit29766f1eb3d8d6cfaf1d6623fb4c3f7e5a822fe4 (patch)
treee356c483e332f2a688d5d9e8edfb7e7a6729af44 /Documentation
parent1dbe83c3445a1604546620a60888cf26b63f8782 (diff)
[PATCH] rcutorture: catchup doc fixes for idle-hz tests
This just catches the RCU torture documentation up with the recent fixes that test RCU for architectures that turn of the scheduling-clock interrupt for idle CPUs and the addition of a SUCCESS/FAILURE indication, fixing up an obsolete comment as well. Signed-off-by: Paul E. McKenney <paulmck@us.ibm.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/RCU/torture.txt12
1 files changed, 11 insertions, 1 deletions
diff --git a/Documentation/RCU/torture.txt b/Documentation/RCU/torture.txt
index e4c38152f7f7..d896685a9100 100644
--- a/Documentation/RCU/torture.txt
+++ b/Documentation/RCU/torture.txt
@@ -35,6 +35,15 @@ stat_interval The number of seconds between output of torture
35 be printed -only- when the module is unloaded, and this 35 be printed -only- when the module is unloaded, and this
36 is the default. 36 is the default.
37 37
38shuffle_interval
39 The number of seconds to keep the test threads affinitied
40 to a particular subset of the CPUs. Used in conjunction
41 with test_no_idle_hz.
42
43test_no_idle_hz Whether or not to test the ability of RCU to operate in
44 a kernel that disables the scheduling-clock interrupt to
45 idle CPUs. Boolean parameter, "1" to test, "0" otherwise.
46
38verbose Enable debug printk()s. Default is disabled. 47verbose Enable debug printk()s. Default is disabled.
39 48
40 49
@@ -119,4 +128,5 @@ The following script may be used to torture RCU:
119 128
120The output can be manually inspected for the error flag of "!!!". 129The output can be manually inspected for the error flag of "!!!".
121One could of course create a more elaborate script that automatically 130One could of course create a more elaborate script that automatically
122checked for such errors. 131checked for such errors. The "rmmod" command forces a "SUCCESS" or
132"FAILURE" indication to be printk()ed.