linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
	paulmck@linux.vnet.ibm.com, jack@suse.cz,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"rusty@rustcorp.com.au" <rusty@rustcorp.com.au>,
	Tejun Heo <tj@kernel.org>,
	Michael Wang <wangyun@linux.vnet.ibm.com>
Subject: Re: WARNING: at kernel/rcutree.c:1558 rcu_do_batch+0x386/0x3a0(), during CPU hotplug
Date: Fri, 14 Sep 2012 20:32:13 +0800	[thread overview]
Message-ID: <20120914123213.GB21038@localhost> (raw)
In-Reply-To: <1347625519.7172.31.camel@twins>

On Fri, Sep 14, 2012 at 02:25:19PM +0200, Peter Zijlstra wrote:
> On Fri, 2012-09-14 at 17:48 +0530, Srivatsa S. Bhat wrote:
> > #! /bin/bash
> 
> CPUPATH="/sys/devices/system/cpu"
> 
> > NUMBER_OF_CPUS=`ls -d /sys/devices/system/cpu/cpu[0-9]* | wc -l`
> 
> apply the above
> 
> > cd /sys/devices/system/cpu
> 
> skip this, so running the script doesn't change PWD

Yes, that's good practice.

> > while [ 1 ]
> 
> while :;

I used to use 'true', but ':' looks cool!

> > do
> >         for ((i=1; i < NUMBER_OF_CPUS; i++))
> >         do
> >                 sleep 1;
> 
> Also play with shorter sleeps like: sleep .1, I've found that higher
> hotplug rate triggers some races faster.

OK.

> >                 state=`cat cpu$i/online`
> >                 if [ $state -eq 0 ]
> >                 then
> >                         echo 1 > cpu$i/online
> >                 else
> >                         echo 0 > cpu$i/online
> 
> 	echo $((state^1)) > $CPUPATH/cpu$i/online

Good!

Thanks,
Fengguang

  reply	other threads:[~2012-09-14 12:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 12:09 WARNING: at kernel/rcutree.c:1550 __rcu_process_callbacks+0x46f/0x4b0() Srivatsa S. Bhat
2012-07-19 17:15 ` Paul E. McKenney
2012-07-20 10:41   ` Srivatsa S. Bhat
2012-07-20 14:36     ` Paul E. McKenney
2012-07-20 14:57       ` Srivatsa S. Bhat
2012-09-12 12:36   ` WARNING: at kernel/rcutree.c:1558 rcu_do_batch+0x386/0x3a0(), during CPU hotplug Srivatsa S. Bhat
2012-09-12 15:31     ` Paul E. McKenney
2012-09-13  6:30       ` Michael Wang
2012-09-13 12:47         ` Srivatsa S. Bhat
2012-09-14  4:33           ` Michael Wang
2012-09-26  9:35           ` Srivatsa S. Bhat
2012-09-27  2:59             ` Michael Wang
2012-09-27 19:06               ` Srivatsa S. Bhat
2012-09-13  8:35     ` Srivatsa S. Bhat
2012-09-14 11:47       ` Fengguang Wu
2012-09-14 12:18         ` Srivatsa S. Bhat
2012-09-14 12:25           ` Peter Zijlstra
2012-09-14 12:32             ` Fengguang Wu [this message]
2012-09-14 12:34             ` Srivatsa S. Bhat
2012-09-14 12:28           ` Fengguang Wu

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=20120914123213.GB21038@localhost \
    --to=fengguang.wu@intel.com \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rusty@rustcorp.com.au \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=wangyun@linux.vnet.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;
as well as URLs for NNTP newsgroup(s).