On Tue, Sep 03, 2013 at 09:22:24AM -0400, Steven Rostedt wrote:
> On Sat, 31 Aug 2013 12:44:31 -0700
> "Paul E. McKenney" wrote:
>
> > On Sat, Aug 31, 2013 at 01:11:20AM -0400, Steven Rostedt wrote:
> > > From: "Steven Rostedt (Red Hat)"
> > >
> > > Since none of the internal ftrace function tr
On Sat, 31 Aug 2013 12:44:31 -0700
"Paul E. McKenney" wrote:
> On Sat, Aug 31, 2013 at 01:11:20AM -0400, Steven Rostedt wrote:
> > From: "Steven Rostedt (Red Hat)"
> >
> > Since none of the internal ftrace function tracing uses RCU in
> > their callbacks, it is OK to set the global_ops (the one
On Sat, Aug 31, 2013 at 01:11:20AM -0400, Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> Since none of the internal ftrace function tracing uses RCU in
> their callbacks, it is OK to set the global_ops (the one that
> they all use) to RCU safe.
>
> Cc: Jiri Olsa
> Cc: Paul E. McKe
On Sat, Aug 31, 2013 at 01:11:20AM -0400, Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> Since none of the internal ftrace function tracing uses RCU in
> their callbacks, it is OK to set the global_ops (the one that
> they all use) to RCU safe.
>
> Cc: Jiri Olsa
> Cc: Paul E. McKe
From: "Steven Rostedt (Red Hat)"
Since none of the internal ftrace function tracing uses RCU in
their callbacks, it is OK to set the global_ops (the one that
they all use) to RCU safe.
Cc: Jiri Olsa
Cc: Paul E. McKenney
Signed-off-by: Steven Rostedt
---
kernel/trace/ftrace.c |4 +++-
1 f
5 matches
Mail list logo
