[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090320194138.GK6698@linux.vnet.ibm.com>
Date: Fri, 20 Mar 2009 12:41:38 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Steven Rostedt <rostedt@...dmis.org>,
LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 0/5] [GIT PULL] updates for tip/tracing/ftrace
On Fri, Mar 20, 2009 at 08:27:21PM +0100, Ingo Molnar wrote:
>
> * Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote:
>
> > On Fri, Mar 20, 2009 at 07:38:49PM +0100, Ingo Molnar wrote:
> > >
> > > * Ingo Molnar <mingo@...e.hu> wrote:
> > >
> > > > > > This looks like it is RCU/stop_machine related. The CPU is
> > > > > > stuck in in stop_machine? I see that rcu_torture is running.
> > > > > > Does this go away if you turn off rcu_torture?
> > > > >
> > > > > Grasping at straws... Does Lai's rcu_barrier() fix help?
> > > >
> > > > which one is that?
> > >
> > > ok, found it. Will know in about ~24 hours whether it helps.
> >
> > http://lkml.org/lkml/2009/3/20/71 was the one I was thinking of,
> > just to double-check.
>
> Yeah - i just picked it up into tip:core/rcu.
>
> I didnt immediately connect the two things, as 'tracer self-test'
> does not lend itself to 'CPU hotplug and RCU race fix' - but indeed
> in the case of the function tracer there's a dependency due to
> stop_machine_run(). Thanks for point it out!
Thanks go to Steve Rostedt -- I just followed up on his stack-trace
analysis here. ;-)
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