[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220801165711.3b7523e7@gandalf.local.home>
Date: Mon, 1 Aug 2022 16:57:11 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Tzvetomir Stoyanov <tz.stoyanov@...il.com>,
Ingo Molnar <mingo@...nel.org>
Subject: Re: [PATCH 2/3] tracing/eprobe: Add eprobe filter support
On Mon, 1 Aug 2022 11:32:25 +0900
"Masami Hiramatsu (Google)" <mhiramat@...nel.org> wrote:
> From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
>
> Add the filter option to the event probe. This is useful if user wants
> to derive a new event based on the condition of the original event.
>
> E.g.
> echo 'e:egroup/stat_runtime_4core sched/sched_stat_runtime \
> runtime=$runtime:u32 if cpu < 4' >> ../dynamic_events
>
> Then it can filter the events only on first 4 cores.
> Note that the fields used for 'if' must be the fields in the original
> events, not eprobe events.
>
> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@...nel.org>
Hi Masami,
Thanks! But I'm not going to be able to add this for this merge window (too
late, it just opened up), because it's a new feature.
I'll take patch 1 though, as that's just a clean up, and then keep the
other two for the next merge window.
-- Steve
Powered by blists - more mailing lists