Re: [PATCH] RCU torture testing

["Paul E. McKenney" <paulmck@us.ibm.com>]

On Mon, Oct 03, 2005 at 05:31:59PM +0200, Arjan van de Ven wrote:
> 
> > Good point -- all I really need for module parameters is the number
> > of readers.  I should be able to have module load start the test and
> > module unload stop it (any problems with this approach?). 
> 
> only one potential gotcha; it means you can't load the system to the
> extend that the shell doesn't get cpu time otherwise the admin can never
> issue the unload. Maybe a time limit on the testing? (optional as module
> parm for all I care)

OK...  I tried both debugfs and modules, and the modules approach turned
out to be much more tester-friendly.  With debugfs, one must do a special
build of the kernel to enable debugfs -- which will also include other
test code that might skew results -- and the fact that debugfs does not
yet seem to have a standard mount point makes scripting less effective.

In contrast, the modules approach can be used even on an already running
kernel that you did not plan to test ahead of time.

So modules it is.  Patch submitted separately.

							Thanx, Paul
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/