[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210608151144.6f4531c1@oasis.local.home>
Date: Tue, 8 Jun 2021 15:11:44 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Andrii Nakryiko <andrii.nakryiko@...il.com>,
Jiri Olsa <jolsa@...nel.org>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andriin@...com>,
Networking <netdev@...r.kernel.org>, bpf <bpf@...r.kernel.org>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...omium.org>, Daniel Xu <dxu@...uu.xyz>,
Viktor Malik <vmalik@...hat.com>
Subject: Re: [PATCH 03/19] x86/ftrace: Make function graph use ftrace
directly
On Tue, 8 Jun 2021 20:51:25 +0200
Jiri Olsa <jolsa@...hat.com> wrote:
> > > + FTRACE_OPS_FL_PID
> > > + FTRACE_OPS_GRAPH_STUB,
> >
> > nit: this looks so weird... Why not define FTRACE_OPS_GRAPH_STUB as
> > zero in case of #ifdef ftrace_graph_func? Then it will be natural and
> > correctly looking | FTRACE_OPS_GRAPH_STUB?
I have no idea why I did that :-/ But it was a while ago when I wrote
this code. I think there was a reason for it, but with various updates,
that reason disappeared.
>
> ok, I can change that
Yes, please do.
Thanks,
-- Steve
Powered by blists - more mailing lists