From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Tom Zanussi <tzanussi@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Li Zefan <lizf@cn.fujitsu.com>, Zhaolei <zhaolei@cn.fujitsu.com>
Subject: [PATCH 0/2][GIT PULL] tracing/filters: adjustements for strings
Date: Sun, 3 May 2009 03:50:31 +0200 [thread overview]
Message-ID: <1241315433-7225-1-git-send-email-fweisbec@gmail.com> (raw)
Hi,
The following patchset includes two little peas of features
for tracing filters, making them able to filter every kind of strings.
Now I can do this:
cd /debug/tracing
echo > trace
echo stacktrace > trace_options
cd events/lockdep
echo 'name == "&REISERFS_SB(s)->lock" && wait_usec > 0' > lock_acquired/filter
echo 1 > lock_acquired/enable
sleep 1
echo 0 > lock_acquired/enable
cat trace
# tracer: nop
#
# TASK-PID CPU# TIMESTAMP FUNCTION
# | | | | |
<...>-6464 [000] 327.448232: lock_acquired: &REISERFS_SB(s)->lock (25058.984 us)
<...>-6464 [000] 327.448233:
<= reiserfs_get_block
<= __block_prepare_write
<= block_write_begin
<= reiserfs_write_begin
<= generic_file_buffered_write
<= __generic_file_aio_write_nolock
<= generic_file_aio_write
<...>-6470 [000] 327.448422: lock_acquired: &REISERFS_SB(s)->lock (25112.702 us)
<...>-6470 [000] 327.448425:
<= reiserfs_update_sd_size
<= reiserfs_write_end
<= generic_file_buffered_write
<= __generic_file_aio_write_nolock
<= generic_file_aio_write
<= do_sync_write
<= reiserfs_file_write
Tom, your filter framework is awesome and very useful!
Thanks :-)
Frederic.
---
The following changes since commit a0e39ed378fb6ba916522764cd508fa7d42ad495:
Heiko Carstens (1):
tracing: fix build failure on s390
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git tracing/filters
Frederic Weisbecker (2):
tracing/filters: support for filters of dynamic sized arrays
tracing/filters: support for operator reserved characters in strings
kernel/trace/trace_events_filter.c | 54 ++++++++++++++++++++++++++++++++++--
1 files changed, 51 insertions(+), 3 deletions(-)
next reply other threads:[~2009-05-03 1:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 1:50 Frederic Weisbecker [this message]
2009-05-03 1:50 ` [PATCH 1/2] tracing/filters: support for filters of dynamic sized arrays Frederic Weisbecker
2009-05-03 1:50 ` [PATCH 2/2] tracing/filters: support for operator reserved characters in strings Frederic Weisbecker
2009-05-03 8:26 ` [PATCH 0/2][GIT PULL] tracing/filters: adjustements for strings Ingo Molnar
2009-05-04 4:47 ` Tom Zanussi
2009-05-04 13:42 ` Steven Rostedt
2009-05-05 4:59 ` Tom Zanussi
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=1241315433-7225-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tzanussi@gmail.com \
--cc=zhaolei@cn.fujitsu.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
all inboxes | Powered by JetHome®