From: Ingo Molnar <mingo@elte.hu>
To: "Tom Zanussi" <tzanussi@gmail.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/4] zedtrace generic kernel filtering
Date: Sat, 28 Feb 2009 10:26:57 +0100 [thread overview]
Message-ID: <20090228092657.GA2869@elte.hu> (raw)
In-Reply-To: <1235725256.8512.88.camel@charm-linux>
* Tom Zanussi <tzanussi@gmail.com> wrote:
> Add generic kernel filtering.
>
> Signed-off-by: Tom Zanussi <tzanussi@gmail.com>
>
> ---
> kernel/trace/trace_binary/Makefile | 2 +-
> kernel/trace/trace_binary/zed.c | 103 +++++++++--
> kernel/trace/trace_binary/zed.h | 15 ++
> kernel/trace/trace_binary/zed_filter.c | 301 ++++++++++++++++++++++++++++++++
> kernel/trace/trace_binary/zed_filter.h | 45 +++++
> kernel/trace/trace_binary/zed_sched.c | 4 +
> 6 files changed, 451 insertions(+), 19 deletions(-)
> create mode 100644 kernel/trace/trace_binary/zed_filter.c
> create mode 100644 kernel/trace/trace_binary/zed_filter.h
Nice!
This fits really nicely into the ftrace principles and i'd love
to see this feature merged into ftrace - would you be interested
in working on that? If so then you can find the latest tracing
tree at:
http://people.redhat.com/mingo/tip.git/README
Note that Steve added explicit field enumeration and 'raw' C
syntax tracepoints to the event tracer earlier today (partly
based on your ideas here), so that would be a good basis to
extend/enhance/fix, if you are interested.
Thanks,
Ingo
next prev parent reply other threads:[~2009-02-28 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 9:00 [PATCH 2/4] zedtrace generic kernel filtering Tom Zanussi
2009-02-28 9:26 ` Ingo Molnar [this message]
2009-03-02 7:29 ` Tom Zanussi
2009-03-02 10:58 ` Ingo Molnar
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=20090228092657.GA2869@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.