From: Steven Rostedt <rostedt@goodmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Chuang Wang <nashuiliang@gmail.com>,
"Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing/eprobe: Iterate trace_eprobe directly
Date: Fri, 11 Aug 2023 13:46:31 -0400 [thread overview]
Message-ID: <20230811134631.3c0c0702@gandalf.local.home> (raw)
In-Reply-To: <20230811105102.f7c1a2d08700df1c226f096f@kernel.org>
On Fri, 11 Aug 2023 10:51:02 +0900
Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
> On Thu, 10 Aug 2023 19:32:04 +0900
> Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
>
> > On Thu, 10 Aug 2023 16:25:23 +0800
> > Chuang Wang <nashuiliang@gmail.com> wrote:
> >
> > > Refer to the description in [1], we can skip "container_of()" following
> > > "list_for_each_entry()" by using "list_for_each_entry()" with
> > > "struct trace_eprobe" and "tp.list".
> > >
> > > [1] https://lore.kernel.org/all/CAHk-=wjakjw6-rDzDDBsuMoDCqd+9ogifR_EE1F0K-jYek1CdA@mail.gmail.com/
> > >
> >
> > Good point. BTW, it is better to have 'for_each_eprobe(ep)' if it repeats 3 times.
>
> Wait, it is for each trace_eprobe on the trace_probe.
>
> #define for_each_trace_eprobe_on_trace_probe(ep, _tp)
> list_for_each_entry(ep, trace_probe_probe_list(_tp), tp.list)
>
Do we need it so verbose? Why can't it just be:
#define for_each_trace_eprobe(ep, tp)
If you are worried about consistency with the for_each_trace_kprobe() then let's call it:
#define for_each_trace_point_eprobe(ep, tp);
-- Steve
prev parent reply other threads:[~2023-08-11 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 8:25 [PATCH] tracing/eprobe: Iterate trace_eprobe directly Chuang Wang
2023-08-10 10:32 ` Masami Hiramatsu
2023-08-11 1:51 ` Masami Hiramatsu
2023-08-11 17:46 ` Steven Rostedt [this message]
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=20230811134631.3c0c0702@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=nashuiliang@gmail.com \
--cc=tz.stoyanov@gmail.com \
/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).