From: Frederic Weisbecker <fweisbec@gmail.com>
To: Tom Zanussi <tzanussi@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 0/4] tracing: event filtering v2
Date: Mon, 23 Mar 2009 00:06:16 +0100 [thread overview]
Message-ID: <20090322230615.GI6002@nowhere> (raw)
In-Reply-To: <1237710626.7703.45.camel@charm-linux>
On Sun, Mar 22, 2009 at 03:30:26AM -0500, Tom Zanussi wrote:
> Hi,
>
> This is version 2 of my patchset adding filtering to the event-tracing
> infrastructure.
>
> Changes from the previous version:
>
> - added common_ prefix to the 5 common event fields
> - ring_buffer_event_discard() fixes from Steven Rostedt
> - changed 'and' and 'or' for compound filters to '&&' and '||'
> - fixed a bug in the matching logic
>
> Everything seems to work ok for me, but I haven't yet gotten around to
> changing the awkward UI. I plan to fix that as soon as I can i.e. allow
> complete compound expressions to be specified all at once, add <, >, <=,
> >= and parens, etc. Until then, it should hopefully be usable for basic
> filtering.
>
> Thanks,
>
> Tom
>
Very nice work!
My events/1 task is pid 4, and swapper (idle) is 0,
cd /debug/tracing/events/sched/sched_switch
echo prev_pid == 4 > filter
echo "&& next_pid == 0" > filter
echo 1 > enable
cat /debug/tracing/trace
# tracer: nop
#
# TASK-PID CPU# TIMESTAMP FUNCTION
# | | | | |
<...>-4 [000] 1136.993069: sched_switch: task events/0:4 [115] ==> swapper:0 [140]
<...>-4 [000] 1136.993081: sched_switch: task events/0:4 [115] ==> swapper:0 [140]
<...>-4 [000] 1137.218492: sched_switch: task events/0:4 [115] ==> swapper:0 [140]
<...>-4 [000] 1137.283787: sched_switch: task events/0:4 [115] ==> swapper:0 [140]
<...>-4 [000] 1137.458733: sched_switch: task events/0:4 [115] ==> swapper:0 [140]
<...>-4 [000] 1137.560932: sched_switch: task events/0:4 [115] ==> swapper:0 [140]
<...>-4 [000] 1137.560941: sched_switch: task events/0:4 [115] ==> swapper:0 [140]
<...>-4 [000] 1137.741107: sched_switch: task events/0:4 [115] ==> swapper:0 [140]
<...>-4 [000] 1138.159083: sched_switch: task events/0:4 [115] ==> swapper:0 [140]
<...>-4 [000] 1138.338673: sched_switch: task events/0:4 [115] ==> swapper:0 [140]
<...>-4 [000] 1138.338681: sched_switch: task events/0:4 [115] ==> swapper:0 [140]
<...>-4 [000] 1138.517769: sched_switch: task events/0:4 [115] ==> swapper:0 [140]
<...>-4 [000] 1138.517833: sched_switch: task events/0:4 [115] ==> swapper:0 [140]
<...>-4 [000] 1138.517845: sched_switch: task events/0:4 [115] ==> swapper:0 [140]
[...]
:-)
prev parent reply other threads:[~2009-03-22 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 8:30 [PATCH 0/4] tracing: event filtering v2 Tom Zanussi
2009-03-22 19:56 ` Ingo Molnar
2009-03-23 8:29 ` Tom Zanussi
2009-03-22 23:06 ` Frederic Weisbecker [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=20090322230615.GI6002@nowhere \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tzanussi@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