[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACueBy7U9+b46YJ6Lbd-c=Nm9KhQyMoXbVOMT4esLYqq7nMt5Q@mail.gmail.com>
Date: Fri, 18 Aug 2023 19:42:33 +0800
From: chuang <nashuiliang@...il.com>
To: Masami Hiramatsu <mhiramat@...nel.org>
Cc: Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH v2] tracing/eprobe: Iterate trace_eprobe directly
OK, I will submit a new patch using "for_each_trace_eprobe_tp".
On Fri, Aug 18, 2023 at 7:03 PM Masami Hiramatsu <mhiramat@...nel.org> wrote:
>
> On Wed, 16 Aug 2023 16:08:50 -0400
> Steven Rostedt <rostedt@...dmis.org> wrote:
>
> > On Sat, 12 Aug 2023 14:20:19 +0900
> > Masami Hiramatsu (Google) <mhiramat@...nel.org> wrote:
> >
> > > > At a minimum, let's call it:
> > > >
> > > > for_each_trace_point_eprobe()
> > >
> > > OK, what about "for_each_trace_eprobe_on()"? I would like to clarify
> > >
> > > - what type is returned
> > > - not all trace_eprobes, but only on the trace_probe.
> > >
> > > Thank you,
> >
> > for_each_trace_eprobe_tp() or for_each_trace_tp_eprobe() ?
>
> for_each_trace_eprobe_tp() is OK for me.
>
> Thanks!
>
> >
> > As it only works for a trace_probe.
> >
> > -- Steve
>
>
> --
> Masami Hiramatsu (Google) <mhiramat@...nel.org>
Powered by blists - more mailing lists