From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linyu Yuan <quic_linyyuan@quicinc.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Tom Zanussi <zanussi@kernel.org>, Ingo Molnar <mingo@redhat.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/3] tracing/probes: allow no event name input when create group
Date: Mon, 6 Jun 2022 23:41:50 +0900 [thread overview]
Message-ID: <20220606234150.43ddad8dd5b459c18a46994d@kernel.org> (raw)
In-Reply-To: <1654171861-24014-1-git-send-email-quic_linyyuan@quicinc.com>
Hi Linyu,
On Thu, 2 Jun 2022 20:10:58 +0800
Linyu Yuan <quic_linyyuan@quicinc.com> wrote:
> take kprobe event as example, when create a group of events,
> p[:[GRP/]EVENT] [MOD:]KSYM[+OFFS]|KADDR [FETCHARGS],
> according to this format, we must input EVENT name,
>
> this change allow only GRP/ input, EVENT name auto generate from KSYM,
> p[:[GRP/][EVENT]] [MOD:]KSYM[+OFFS]|KADDR [FETCHARGS]
>
> siliar change apply to eprobe and uprobe.
Thanks for updating the series. This looks godd to me.
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
for this series.
Thank you!
>
> V1: https://lore.kernel.org/lkml/1651397651-30454-1-git-send-email-quic_linyyuan@quicinc.com/
>
> V2: fix remove comment in V1 patch1,
> remove v1 patch2 as it is NACK.
>
> v3: (v2 link: https://lore.kernel.org/lkml/1653795294-19764-1-git-send-email-quic_linyyuan@quicinc.com/)
> add selftest cases for kprobe and eprobe event,
> remove macro used in v1,v2,
> change location to generate eprobe event name.
>
> v4: (v3 link: https://lore.kernel.org/lkml/1653978552-18637-1-git-send-email-quic_linyyuan@quicinc.com/)
> fix comment of kprobe/eprobe test case.
>
> Linyu Yuan (3):
> tracing: eprobe: remove duplicate is_good_name() operation
> tracing: auto generate event name when create a group of events
> selftests/ftrace: add test case for GRP/ only input
>
> Documentation/trace/kprobetrace.rst | 8 +++----
> Documentation/trace/uprobetracer.rst | 8 +++----
> kernel/trace/trace.c | 8 +++----
> kernel/trace/trace_dynevent.c | 2 +-
> kernel/trace/trace_eprobe.c | 25 +++++++++++-----------
> kernel/trace/trace_kprobe.c | 16 ++++++++------
> kernel/trace/trace_probe.c | 6 ++++++
> kernel/trace/trace_uprobe.c | 12 +++++++----
> .../ftrace/test.d/dynevent/add_remove_eprobe.tc | 9 +++++++-
> .../ftrace/test.d/dynevent/add_remove_kprobe.tc | 7 ++++++
> 10 files changed, 64 insertions(+), 37 deletions(-)
>
> --
> 2.7.4
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2022-06-06 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 12:10 Linyu Yuan
2022-06-02 12:10 ` [PATCH v4 1/3] tracing: eprobe: remove duplicate is_good_name() operation Linyu Yuan
2022-06-13 21:01 ` Tom Zanussi
2022-06-14 0:48 ` Linyu Yuan
2022-06-20 18:38 ` Tom Zanussi
2022-06-21 0:56 ` Linyu Yuan
2022-06-02 12:11 ` [PATCH v4 2/3] tracing: auto generate event name when create a group of events Linyu Yuan
2022-06-02 12:11 ` [PATCH v4 3/3] selftests/ftrace: add test case for GRP/ only input Linyu Yuan
2022-06-06 14:41 ` Masami Hiramatsu [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=20220606234150.43ddad8dd5b459c18a46994d@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=quic_linyyuan@quicinc.com \
--cc=rostedt@goodmis.org \
--cc=zanussi@kernel.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
all inboxes | Powered by JetHome®