From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Tom Zanussi <zanussi@kernel.org>,
Tzvetomir Stoyanov <tz.stoyanov@gmail.com>,
Yordan Karadzhov <y.karadz@gmail.com>
Subject: Re: [PATCH v2] tracing: Fix event probe removal from dynamic events
Date: Wed, 13 Oct 2021 23:32:44 +0900 [thread overview]
Message-ID: <20211013233244.46341468a06ba43895b99c0e@kernel.org> (raw)
In-Reply-To: <20211012201559.5f0ad249@gandalf.local.home>
On Tue, 12 Oct 2021 20:15:59 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Wed, 13 Oct 2021 07:46:11 +0900
> Masami Hiramatsu <mhiramat@kernel.org> wrote:
>
> > The first argument check should be optional. If the event name matches and
> > the system name is NULL but argc == 0, it should return true.
> > (please consider it is a wild card like "-:*/EVENT *")
> > So if the argc == 0 please skip below and check the event name and
> > the system name.
>
> OK, so I'll make them all optional, but at least, if they are supplied,
> they will be checked.
>
> That is, you can't add the options if you don't add the event as well. But
> if you do add the event, then it should work.
>
> Basically, we have the following:
>
> # echo 'e:hrstate timer/hrtimer_cancel state=+0x38($hrtimer):u8' >> dynamic_events
> # cat dynamic_events
> eprobes/hrstate timer.hrtimer_cancel state=+0x38($hrtimer):u8
>
> Then the following should work:
>
> # echo '-:hrstate timer/hrtimer_cancel state=+0x38($hrtimer):u8' >> dynamic_events
> # echo '-:eprobes/hrstate timer.hrtimer_cancel state=+0x38($hrtimer):u8' >> dynamic_events
> # echo '-:eprobes/hrstate timer.hrtimer_cancel' >> dynamic_events
> # echo '-:eprobes/hrstate' >> dynamic_events
Agreed.
>
> But the following will not work:
>
> # echo '-:hrstate state=+0x38($hrtimer):u8' >> dynamic_events
> # echo '-:hrstate timer.hrtimer_cancel state=+0x38($hrtimer):u8' >> dynamic_events
> # echo '-:hrstate timer.hrtimer_cancel' >> dynamic_events
The first one is agreed. But the rest 2 cases should work because it just omits the
group name. At least {k,u}probe events work.
> Should this work?
>
> # echo '-:hrstate' >> dynamic_events
Yes. In this case, all dynamic events which have "hrstate" event name are removed.
Thank you,
>
> -- Steve
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2021-10-13 14:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 12:19 Steven Rostedt
2021-10-12 14:31 ` Masami Hiramatsu
2021-10-12 16:03 ` Steven Rostedt
2021-10-12 22:42 ` Masami Hiramatsu
2021-10-13 0:08 ` Steven Rostedt
2021-10-13 14:42 ` Masami Hiramatsu
2021-10-13 16:53 ` Steven Rostedt
2021-10-12 22:46 ` Masami Hiramatsu
2021-10-13 0:15 ` Steven Rostedt
2021-10-13 14:32 ` Masami Hiramatsu [this message]
2021-10-13 15:09 ` 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=20211013233244.46341468a06ba43895b99c0e@kernel.org \
--to=mhiramat@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tz.stoyanov@gmail.com \
--cc=y.karadz@gmail.com \
--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®