[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200213223254.668a340d@oasis.local.home>
Date: Thu, 13 Feb 2020 22:32:54 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.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
Subject: Re: [PATCH v2 9/9] perf,tracing: Allow function tracing when !RCU
On Fri, 14 Feb 2020 11:42:45 +0900
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com> wrote:
> > > +++ 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.
:-)
-- Steve
Powered by blists - more mailing lists