[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1377981074.26624.0.camel@pippen.local.home>
Date: Sat, 31 Aug 2013 16:31:14 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: paulmck@...ux.vnet.ibm.com
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Jiri Olsa <jolsa@...hat.com>
Subject: Re: [RFC][PATCH 08/18 v2] ftrace/rcu: Do not trace
debug_lockdep_rcu_enabled()
On Sat, 2013-08-31 at 12:21 -0700, Paul E. McKenney wrote:
> On Sat, Aug 31, 2013 at 01:11:25AM -0400, Steven Rostedt wrote:
> > From: "Steven Rostedt (Red Hat)" <rostedt@...dmis.org>
> >
> > The function debug_lockdep_rcu_enabled() is part of the RCU lockdep
> > debugging, and is called very frequently. I found that if I enable
> > a lot of debugging and run the function graph tracer, this
> > function can cause a live lock of the system.
> >
> > We don't usually trace lockdep infrastructure, no need to trace
> > this either.
> >
> > Cc: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> > Signed-off-by: Steven Rostedt <rostedt@...dmis.org>
>
> Reviewed-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
>
> Or I can just take it, if you would rather. (If so, 3.12 or 3.13?)
>
Feel free to take it and I'll remove it from my queue. 3.12 please.
I'll just need to remember to turn off function graph tracing when
testing these patches again.
-- Steve
--
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