[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200214024244.GH36551@google.com>
Date: Fri, 14 Feb 2020 11:42:45 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
rostedt@...dmis.org, mingo@...nel.org, joel@...lfernandes.org,
gregkh@...uxfoundation.org, gustavo@...eddedor.com,
tglx@...utronix.de, paulmck@...nel.org, josh@...htriplett.org,
mathieu.desnoyers@...icios.com, jiangshanlai@...il.com,
sergey.senozhatsky.work@...il.com
Subject: Re: [PATCH v2 9/9] perf,tracing: Allow function tracing when !RCU
On (20/02/14 11:28), Sergey Senozhatsky wrote:
> On (20/02/12 22:01), Peter Zijlstra wrote:
> > Since perf is now able to deal with !rcu_is_watching() contexts,
> > remove the restraint.
> >
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@...radead.org>
> > ---
> > kernel/trace/trace_event_perf.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > --- a/kernel/trace/trace_event_perf.c
> > +++ b/kernel/trace/trace_event_perf.c
> > @@ -477,7 +477,7 @@ static int perf_ftrace_function_register
> > {
> > struct ftrace_ops *ops = &event->ftrace_ops;
> >
> > - ops->flags = FTRACE_OPS_FL_RCU;
> > + ops->flags = 0;
>
> FTRACE_OPS_FL_ENABLED?
No, never mind.
-ss
Powered by blists - more mailing lists