Re: [RFC][PATCH 15/18 v2] ftrace/rcu: Mark functions that are RCU unsafe

2013-08-31 Thread Paul E. McKenney
On Sat, Aug 31, 2013 at 04:43:24PM -0400, Steven Rostedt wrote: > On Sat, 2013-08-31 at 13:00 -0700, Paul E. McKenney wrote: > > On Sat, Aug 31, 2013 at 01:11:32AM -0400, Steven Rostedt wrote: > > > From: "Steven Rostedt (Red Hat)" > > > > > > Some callbacks of the function tracer use rcu_read_lo

Re: [RFC][PATCH 15/18 v2] ftrace/rcu: Mark functions that are RCU unsafe

2013-08-31 Thread Steven Rostedt
On Sat, 2013-08-31 at 13:00 -0700, Paul E. McKenney wrote: > On Sat, Aug 31, 2013 at 01:11:32AM -0400, Steven Rostedt wrote: > > From: "Steven Rostedt (Red Hat)" > > > > Some callbacks of the function tracer use rcu_read_lock(). This means that > > there's places that can not be traced because RC

Re: [RFC][PATCH 15/18 v2] ftrace/rcu: Mark functions that are RCU unsafe

2013-08-31 Thread Paul E. McKenney
On Sat, Aug 31, 2013 at 01:11:32AM -0400, Steven Rostedt wrote: > From: "Steven Rostedt (Red Hat)" > > Some callbacks of the function tracer use rcu_read_lock(). This means that > there's places that can not be traced because RCU is not tracking the CPU > for various reasons (like NO_HZ_FULL and