From: Tom Zanussi <zanussi@kernel.org>
To: Linyu Yuan <quic_linyyuan@quicinc.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/4] tracing/probes: allow no event name input when create group
Date: Tue, 05 Jul 2022 16:46:32 -0500 [thread overview]
Message-ID: <725b7b32d65b4026313f658954f9f7ad31bd2c64.camel@kernel.org> (raw)
In-Reply-To: <1656296348-16111-1-git-send-email-quic_linyyuan@quicinc.com>
Hi Yuan,
On Mon, 2022-06-27 at 10:19 +0800, Linyu Yuan 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]
>
> similar change apply to eprobe and uprobe.
Thanks for making those changes!
For the series,
Reviewed-by: Tom Zanussi <zanussi@kernel.org>
Tom
>
> V2: (v1:
> https://lore.kernel.org/lkml/1651397651-30454-1-git-send-email-quic_linyyuan@quicinc.com/
> )
> fix remove comment in V1 patch1,
> remove v1 patch2 as it is NACK.
>
> v3: (v2 :
> 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 :
> https://lore.kernel.org/lkml/1653978552-18637-1-git-send-email-quic_linyyuan@quicinc.com/
> )
> fix comment of kprobe/eprobe test case.
>
> v5: (v4:
> https://lore.kernel.org/lkml/1654171861-24014-1-git-send-email-quic_linyyuan@quicinc.com/
> )
> for eprobe, when only input a "SYSTEM.", it is invalid.
> add Acked-by from Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> v6: (v5:
> https://lore.kernel.org/lkml/1655168698-19898-1-git-send-email-quic_linyyuan@quicinc.com/
> )
> change some code order according review comment from Tom Zanussi,
> some minor changes.
>
> v7: (v6:
> https://lore.kernel.org/lkml/1655776787-18133-1-git-send-email-quic_linyyuan@quicinc.com/
> )
> move log index to a separate patch according review comment
>
> Linyu Yuan (4):
> tracing: eprobe: add missing log index
> 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 | 28 +++++++++++-
> ----------
> kernel/trace/trace_kprobe.c | 16 ++++++++----
> -
> kernel/trace/trace_probe.c | 4 ++++
> 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(+), 38 deletions(-)
>
next prev parent reply other threads:[~2022-07-05 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 2:19 Linyu Yuan
2022-06-27 2:19 ` [PATCH v7 1/4] tracing: eprobe: add missing log index Linyu Yuan
2022-06-27 2:19 ` [PATCH v7 2/4] tracing: eprobe: remove duplicate is_good_name() operation Linyu Yuan
2022-06-27 2:19 ` [PATCH v7 3/4] tracing: auto generate event name when create a group of events Linyu Yuan
2022-06-27 2:19 ` [PATCH v7 4/4] selftests/ftrace: add test case for GRP/ only input Linyu Yuan
2022-07-05 21:46 ` Tom Zanussi [this message]
2022-07-12 19:55 ` [PATCH v7 0/4] tracing/probes: allow no event name input when create group Steven Rostedt
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=725b7b32d65b4026313f658954f9f7ad31bd2c64.camel@kernel.org \
--to=zanussi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=quic_linyyuan@quicinc.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
all inboxes | Powered by JetHome®