Re: [PATCH] RCU torture-testing kernel module

[Badari Pulavarty <pbadari@gmail.com>]

On Mon, 2005-10-24 at 15:54 -0700, Paul E. McKenney wrote:
> On Mon, Oct 24, 2005 at 09:24:33AM -0700, Badari Pulavarty wrote:
> > On Sun, 2005-10-23 at 17:47 -0700, Paul E. McKenney wrote:
> > > On Sun, Oct 23, 2005 at 12:05:21PM -0700, Andrew Morton wrote:
> > > > Ingo Oeser <ioe-lkml@rameria.de> wrote:
> > > > >
> > > > > DEBUG_KERNEL should do nothing more than showing the debugging
> > > > >  options. 
> > > > 
> > > > yup.
> > > > 
> > > > >  E.g. I don't expect to enable any additional code in an 
> > > > >  unrelated file, if I enable Magic-SysRQ on an embedded, unattended device
> > > > >  to be able to analyze potential problems via serial console.
> > > > > 
> > > > >  @Andrew: Would you accept a patch to fix that?
> > > > 
> > > > more yup.
> > > 
> > > OK, the attached patch covers this and also fixes the redundant #include
> > > that Greg KH spotted.
> > > 
> > > Thoughts?
> > 
> > Paul,
> > 
> > I enabled RCU_TORTURE_TEST in 2.6.14-rc5-mm1. My machine took 10+
> > minutes to boot and let me login. RCU kthreads are hogging the CPU. 
> > Is this expected ? 
> 
> If you did CONFIG_RCU_TORTURE_TEST=y, then yes.

Yep. I have a bad habit of saying "y" to all interesting stuff
in -mm kernel (while doing make oldconfig). I don't use "modules",
initrd etc..

I compiled it as a module. No harm done :)

Thanks,
Badari