[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180327104242.3594bcac@gandalf.local.home>
Date: Tue, 27 Mar 2018 10:42:42 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc: Alexei Starovoitov <ast@...com>,
"David S. Miller" <davem@...emloft.net>,
Daniel Borkmann <daniel@...earbox.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
netdev <netdev@...r.kernel.org>,
kernel-team <kernel-team@...com>,
linux-api <linux-api@...r.kernel.org>
Subject: Re: [PATCH v6 bpf-next 07/11] tracepoint: introduce
kernel_tracepoint_find_by_name
On Tue, 27 Mar 2018 10:18:24 -0400 (EDT)
Mathieu Desnoyers <mathieu.desnoyers@...icios.com> wrote:
> ----- On Mar 27, 2018, at 10:07 AM, rostedt rostedt@...dmis.org wrote:
>
> > On Mon, 26 Mar 2018 19:47:02 -0700
> > Alexei Starovoitov <ast@...com> wrote:
> >
> >> From: Alexei Starovoitov <ast@...nel.org>
> >>
> >> introduce kernel_tracepoint_find_by_name() helper to let bpf core
> >> find tracepoint by name and later attach bpf probe to a tracepoint
> >>
> >> Signed-off-by: Alexei Starovoitov <ast@...nel.org>
> >
> > Reviewed-by: Steven Rostedt (VMware) <rostedt@...dmis.org>
>
> Steven showed preference for tracepoint_kernel_find_by_name() at some
> point (starting with a tracepoint_ prefix). I'm find with either of
> the names.
Yeah, I do prefer tracepoint_kernel_find_by_name() to stay consistent
with the other tracepoint functions. But we have
"for_each_kernel_tracepoint()" and not "for_each_tracepoint_kernel()",
thus we need to pick being consistent with one or the other. One answer
is to use tracpoint_kernel_find_by_name() and rename the for_each to
for_each_tracpoint_kernel().
-- Steve
>
> Reviewed-by: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
>
> Thanks,
>
> Mathieu
>
> >
> > Thanks for doing this Alexei!
> >
> > One nit below.
Powered by blists - more mailing lists