From: Tom Zanussi <tzanussi@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Steven Rostedt" <rostedt@goodmis.org>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/4] zedtrace generic kernel filtering
Date: Mon, 02 Mar 2009 01:29:49 -0600 [thread overview]
Message-ID: <1235978989.7581.46.camel@charm-linux> (raw)
In-Reply-To: <20090228092657.GA2869@elte.hu>
On Sat, 2009-02-28 at 10:26 +0100, Ingo Molnar wrote:
> * 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!
>
Thanks!
> 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
Sure, but I'm not too familiar with the ftrace code and wouldn't have
big blocks of time to devote to it, so if it's something that's needed
"right away", I'll probably have to defer to letting someone else adapt
the code if they wanted to.
> 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.
>
Yeah, I took a quick look and saw some nice improvements. Anyway, the
filtering I did for this was basically a side-effect of the event
description stuff, which made the filtering relatively easy to do (and
the event description files give the user a way to list the available
fields). What I'm wondering is if you're interested in the filtering
part alone or in the event description part as well, which I hadn't
thought of as separable (I guess I need to look at the current ftrace
code to see what's already there).
Thanks,
Tom
> Thanks,
>
> Ingo
next prev parent reply other threads:[~2009-03-02 7:30 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
2009-03-02 7:29 ` Tom Zanussi [this message]
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=1235978989.7581.46.camel@charm-linux \
--to=tzanussi@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
/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