From: Tom Zanussi <tzanussi@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Li Zefan <lizf@cn.fujitsu.com>, Zhaolei <zhaolei@cn.fujitsu.com>,
Theodore Tso <tytso@mit.edu>
Subject: Re: [PATCH 0/2][GIT PULL] tracing/filters: adjustements for strings
Date: Mon, 04 May 2009 23:59:09 -0500 [thread overview]
Message-ID: <1241499549.6825.4.camel@tropicana> (raw)
In-Reply-To: <alpine.DEB.2.00.0905040937350.3785@gandalf.stny.rr.com>
Hi,
On Mon, 2009-05-04 at 09:42 -0400, Steven Rostedt wrote:
>
> On Sun, 3 May 2009, Frederic Weisbecker wrote:
>
> > 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 :-)
>
> I totally agree, and also like Frederic's changes.
>
> But...
>
>
> This is all useless unless people know it exists and more importantly, how
> to use it.
>
> Ted Tso already started a Documentation/trace/events.txt. We need to add
> documentation of this feature either in Doc../trace/events.txt or add a
> new file called Doc../trace/filters.txt. Probably would be better to add
> a separate file, and add a "See filters.txt" in events.txt.
>
> Tom or Frederic, could either of you write something up? I could when I
> have time. The git logs seems to be pretty good at explaining it.
>
Sure, I'll write something up and put it in Doc../trace/filters.txt.
Tom
> Thanks,
>
> -- Steve
>
prev parent reply other threads:[~2009-05-05 4:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 1:50 Frederic Weisbecker
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 [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=1241499549.6825.4.camel@tropicana \
--to=tzanussi@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tytso@mit.edu \
--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®