diff options
author | Paul E. McKenney <paulmck@us.ibm.com> | 2006-06-27 02:54:02 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-06-27 17:32:40 -0700 |
commit | 29766f1eb3d8d6cfaf1d6623fb4c3f7e5a822fe4 (patch) | |
tree | e356c483e332f2a688d5d9e8edfb7e7a6729af44 /Documentation/RCU | |
parent | 1dbe83c3445a1604546620a60888cf26b63f8782 (diff) | |
download | linux-3.10-29766f1eb3d8d6cfaf1d6623fb4c3f7e5a822fe4.tar.gz linux-3.10-29766f1eb3d8d6cfaf1d6623fb4c3f7e5a822fe4.tar.bz2 linux-3.10-29766f1eb3d8d6cfaf1d6623fb4c3f7e5a822fe4.zip |
[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/RCU')
-rw-r--r-- | Documentation/RCU/torture.txt | 12 |
1 files changed, 11 insertions, 1 deletions
diff --git a/Documentation/RCU/torture.txt b/Documentation/RCU/torture.txt index e4c38152f7f..d896685a910 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 be printed -only- when the module is unloaded, and this is the default. +shuffle_interval + The number of seconds to keep the test threads affinitied + to a particular subset of the CPUs. Used in conjunction + with test_no_idle_hz. + +test_no_idle_hz Whether or not to test the ability of RCU to operate in + a kernel that disables the scheduling-clock interrupt to + idle CPUs. Boolean parameter, "1" to test, "0" otherwise. + verbose Enable debug printk()s. Default is disabled. @@ -119,4 +128,5 @@ The following script may be used to torture RCU: The output can be manually inspected for the error flag of "!!!". One could of course create a more elaborate script that automatically -checked for such errors. +checked for such errors. The "rmmod" command forces a "SUCCESS" or +"FAILURE" indication to be printk()ed. |