public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, matthltc@us.ibm.com, dipankar@in.ibm.com,
	arjan@infradead.org, ioe-lkml@rameria.de, greg@kroah.com,
	pbadari@us.ibm.com, mrmacman_g4@mac.com, hugh@veritas.com,
	vatsa@in.ibm.com
Subject: [PATCH 1/3] rcutorture: catchup doc fixes for idle-hz tests
Date: Mon, 26 Jun 2006 11:52:47 -0700	[thread overview]
Message-ID: <20060626185247.GA2141@us.ibm.com> (raw)
In-Reply-To: <20060626184821.GA2091@us.ibm.com>

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>
---

 Documentation/RCU/torture.txt |   12 +++++++++++-
 kernel/rcutorture.c           |    2 +-
 2 files changed, 12 insertions(+), 2 deletions(-)

diff -urpNa -X dontdiff linux-2.6.17/Documentation/RCU/torture.txt linux-2.6.17-torturedoc/Documentation/RCU/torture.txt
--- linux-2.6.17/Documentation/RCU/torture.txt	2006-06-17 18:49:35.000000000 -0700
+++ linux-2.6.17-torturedoc/Documentation/RCU/torture.txt	2006-06-24 11:34:36.000000000 -0700
@@ -35,6 +35,15 @@ stat_interval	The number of seconds betw
 		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 tort
 
 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.
diff -urpNa -X dontdiff linux-2.6.17/kernel/rcutorture.c linux-2.6.17-torturedoc/kernel/rcutorture.c
--- linux-2.6.17/kernel/rcutorture.c	2006-06-17 18:49:35.000000000 -0700
+++ linux-2.6.17-torturedoc/kernel/rcutorture.c	2006-06-23 16:28:08.000000000 -0700
@@ -1,5 +1,5 @@
 /*
- * Read-Copy Update /proc-based torture test facility
+ * Read-Copy Update module-based torture test facility
  *
  * This program is free software; you can redistribute it and/or modify
  * it under the terms of the GNU General Public License as published by

  reply	other threads:[~2006-06-26 18:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26 18:48 [PATCH 0/3] 2.6.17 rcutorture: add ops vector to test multiple RCUs Paul E. McKenney
2006-06-26 18:52 ` Paul E. McKenney [this message]
2006-06-26 18:55 ` [PATCH 2/3] rcutorture: add ops vector and Classic RCU ops Paul E. McKenney
2006-06-26 18:58 ` [PATCH 0/3] rcutorture: add call_rcu_bh() operations Paul E. McKenney
2006-06-26 19:17   ` Paul E. McKenney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060626185247.GA2141@us.ibm.com \
    --to=paulmck@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=dipankar@in.ibm.com \
    --cc=greg@kroah.com \
    --cc=hugh@veritas.com \
    --cc=ioe-lkml@rameria.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthltc@us.ibm.com \
    --cc=mrmacman_g4@mac.com \
    --cc=pbadari@us.ibm.com \
    --cc=vatsa@in.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox