[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 2 Feb 2012 09:56:46 -0800
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Josh Triplett <josh@...htriplett.org>
Cc: linux-kernel@...r.kernel.org, mingo@...e.hu, laijs@...fujitsu.com,
dipankar@...ibm.com, akpm@...ux-foundation.org,
mathieu.desnoyers@...ymtl.ca, niv@...ibm.com, tglx@...utronix.de,
peterz@...radead.org, rostedt@...dmis.org, Valdis.Kletnieks@...edu,
dhowells@...hat.com, eric.dumazet@...il.com, darren@...art.com,
fweisbec@...il.com, patches@...aro.org,
"Paul E. McKenney" <paul.mckenney@...aro.org>
Subject: Re: [PATCH RFC tip/core/rcu 30/41] rcutorture: Permit holding off
CPU-hotplug operations during boot
On Wed, Feb 01, 2012 at 09:43:00PM -0800, Josh Triplett wrote:
> On Wed, Feb 01, 2012 at 11:41:48AM -0800, Paul E. McKenney wrote:
> > When rcutorture is started automatically at boot time, it might well
> > also start CPU-hotplug operations at that time, which might not be
> > desirable. This commit therefore adds an rcutorture parameter that
> > allows CPU-hotplug operations to be held off for the specified number
> > of seconds after the start of boot.
> > --- a/Documentation/RCU/torture.txt
> > +++ b/Documentation/RCU/torture.txt
> > @@ -271,11 +278,13 @@ The following script may be used to torture RCU:
> > #!/bin/sh
> >
> > modprobe rcutorture
> > - sleep 100
> > + sleep 3600
> > rmmod rcutorture
> > dmesg | grep torture:
>
> This looks like an entirely unrelated change.
I suppose it is. I did split it out, though a one-line documentation change
seems a bit lightweight for a commit.
Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists