linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Chuang Wang <nashuiliang@gmail.com>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tracing/eprobe: Iterate trace_eprobe directly
Date: Fri, 18 Aug 2023 20:02:58 +0900	[thread overview]
Message-ID: <20230818200258.7f318bab352508c54ed53e83@kernel.org> (raw)
In-Reply-To: <20230816160850.48fa95b6@gandalf.local.home>

On Wed, 16 Aug 2023 16:08:50 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> On Sat, 12 Aug 2023 14:20:19 +0900
> Masami Hiramatsu (Google) <mhiramat@kernel.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@kernel.org>

  reply	other threads:[~2023-08-18 11:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11  8:12 [PATCH v2] tracing/eprobe: Iterate trace_eprobe directly Chuang Wang
2023-08-11 11:48 ` Masami Hiramatsu
2023-08-11 19:45 ` Steven Rostedt
2023-08-12  5:20   ` Masami Hiramatsu
2023-08-16 20:08     ` Steven Rostedt
2023-08-18 11:02       ` Masami Hiramatsu [this message]
2023-08-18 11:42         ` chuang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230818200258.7f318bab352508c54ed53e83@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=nashuiliang@gmail.com \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).