From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 1/2 v2] tracing/ftrace: handle more than one stat file per tracer
Date: Thu, 8 Jan 2009 09:58:18 +0100 [thread overview]
Message-ID: <20090108085817.GA6560@nowhere> (raw)
In-Reply-To: <alpine.DEB.1.10.0901072249510.2429@gandalf.stny.rr.com>
On Wed, Jan 07, 2009 at 10:50:35PM -0500, Steven Rostedt wrote:
>
> On Wed, 7 Jan 2009, Frederic Weisbecker wrote:
>
> > Impact: new API for tracers
> >
> > Make the stat tracing API reentrant. And also provide the new directory
> > /debugfs/tracing/trace_stat which will contain all the stat files for the
> > current active tracer.
> >
> > Now a tracer will, if desired, want to provide a zero terminated array of
> > tracer_stat structures.
> > Each one contains the callbacks necessary for one stat file.
> > It have to provide at least a name for its stat file, an iterator with
> > stat_start/start_next callback and an output callback for one stat entry.
> >
> > Changes in v2:
> >
>
> Hi Frederic,
>
> This patch fails to compile the branch tracer by itself. No patch should
> break a build (for bisecting reasons).
>
> -- Steve
>
Hmm. Yes, so perhaps I can resend the two patches in one?
next prev parent reply other threads:[~2009-01-08 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 21:40 [PATCH 1/2 v2] tracing/ftrace: handle more than one stat file per tracer Frederic Weisbecker
2009-01-08 3:50 ` Steven Rostedt
2009-01-08 8:58 ` Frederic Weisbecker [this message]
2009-01-08 14:24 ` Steven Rostedt
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=20090108085817.GA6560@nowhere \
--to=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