From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
tzanussi@gmail.com, lizf@cn.fujitsu.com, fweisbec@gmail.com,
tglx@linutronix.de
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:tracing/core] tracing/filters: Provide basic regex support
Date: Sat, 26 Sep 2009 06:10:05 -0400 [thread overview]
Message-ID: <1253959805.12145.95.camel@frodo> (raw)
In-Reply-To: <tip-1889d20922d14a97b2099fa4d47587217c0ba48b@git.kernel.org>
On Fri, 2009-09-25 at 06:19 +0000, tip-bot for Frederic Weisbecker
wrote:
> Commit-ID: 1889d20922d14a97b2099fa4d47587217c0ba48b
> Gitweb: http://git.kernel.org/tip/1889d20922d14a97b2099fa4d47587217c0ba48b
> Author: Frederic Weisbecker <fweisbec@gmail.com>
> AuthorDate: Thu, 24 Sep 2009 21:10:44 +0200
> Committer: Frederic Weisbecker <fweisbec@gmail.com>
> CommitDate: Thu, 24 Sep 2009 21:39:27 +0200
>
> tracing/filters: Provide basic regex support
>
> This patch provides basic support for regular expressions in filters.
>
> It supports the following types of regexp:
>
> - *match_beginning
> - *match_middle*
> - match_end*
> - !don't match
>
> Example:
> cd /debug/tracing/events/bkl/lock_kernel
> echo 'file == "*reiserfs*"' > filter
> echo 1 > enable
Darn! I need to keep up with my email more. Someone asked me at my
ftrace tutorial if the filters can take regex's. I told them that I
don't think so. Of course, my tutorial was on 2.6.31 so I was still
correct. But it would have been nice if I told them that it will in
2.6.32 or 33.
-- Steve
>
> gedit-4941 [000] 457.735437: lock_kernel: depth: 0, fs/reiserfs/namei.c:334 reiserfs_lookup()
> sync_supers-227 [001] 461.379985: lock_kernel: depth: 0, fs/reiserfs/super.c:69 reiserfs_sync_fs()
> sync_supers-227 [000] 461.383096: lock_kernel: depth: 0, fs/reiserfs/journal.c:1069 flush_commit_list()
> reiserfs/1-1369 [001] 461.479885: lock_kernel: depth: 0, fs/reiserfs/journal.c:3509 flush_async_commits()
>
> Every string is now handled as a regexp in the filter framework, which
> helps to factorize the code for handling both simple strings and
> regexp comparisons.
>
> (The regexp parsing code has been wildly cherry picked from ftrace.c
> written by Steve.)
>
> v2: Simplify the whole and drop the filter_regex file
next parent reply other threads:[~2009-09-26 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-1889d20922d14a97b2099fa4d47587217c0ba48b@git.kernel.org>
2009-09-26 10:10 ` Steven Rostedt [this message]
2009-09-28 8:50 ` [tip:tracing/core] tracing/filters: Provide basic regex support Frederic Weisbecker
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=1253959805.12145.95.camel@frodo \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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