public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	David Sharp <dhsharp@google.com>,
	Arjan van de Ven <arjan@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC tracing] Common Trace Format for Linux (v1.1)
Date: Thu, 11 Nov 2010 07:26:46 -0500	[thread overview]
Message-ID: <20101111122645.GA3992@Krystal> (raw)
In-Reply-To: <alpine.LFD.2.00.1011111011530.2900@localhost6.localdomain6>

* Thomas Gleixner (tglx@linutronix.de) wrote:
> Mathieu,
> 
> On Wed, 10 Nov 2010, Mathieu Desnoyers wrote:
> 
> > * Thomas Gleixner (tglx@linutronix.de) wrote:
> > [...]
> > 
> > > The requirement list has been beaten to death several times already
> > > along with the various options of trace formats, so we really are at
> > > the point where you folks need to sit down and come up with real code
> > > which can be discussed and improved on a technical base.
> > 
> > I understand and share your frustration about things having been standing still
> > for way too long.
> > 
> > In order to get things rolling, I hereby append my trace format proposal as RFC.
> > I did implement the core elements of it already in the BabelTrace trace
> > converter project, so it's not one of these dreaded "design by committee without
> > any understanding of the practicality aspects" standards. I try make sure it
> > translates to something realistic and useful.
> > 
> > Feedback is welcome, thanks,
> > 
> > Mathieu
> > 
> > RFC: Common Trace Format Proposal for Linux (v1.1)
> 
> Groan. Did you read what I wrote ?
> 
> > >                                              ... so we really are at
> > > the point where you folks need to sit down and come up with real code
> > > which can be discussed and improved on a technical base.
> 
> Your reaction on this is to send yet another proposal, which has not
> really anything new in it.
> 
> What we are waiting for is a sensible incremental patch series, which
> extends or replaces functionality in the existing perf ABI up to the
> point, where we can eventually see the need for a sensible
> replacement. That's the way we work, not with tons of proposals.

OK, I'll work on this. Meanwhile, anyone interested to provide feedback on the
RFC I sent is still welcome to do so.

Thanks,

Mathieu


-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com

  reply	other threads:[~2010-11-11 12:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11  0:46 [RFD tracing] Tracing ABI Work Plan Mathieu Desnoyers
2010-11-11  1:33 ` Thomas Gleixner
2010-11-11  1:50   ` Steven Rostedt
2010-11-11  1:55     ` Thomas Gleixner
2010-11-11  2:05       ` Steven Rostedt
2010-11-11  9:10         ` Thomas Gleixner
2010-11-11  2:16   ` [RFC tracing] Common Trace Format for Linux (v1.1) Mathieu Desnoyers
2010-11-11  9:45     ` Thomas Gleixner
2010-11-11 12:26       ` Mathieu Desnoyers [this message]
2010-11-11  7:59 ` [RFD tracing] Tracing ABI Work Plan Masami Hiramatsu
2010-11-11 13:02   ` Mathieu Desnoyers
2010-11-12 11:20     ` Masami Hiramatsu
2010-11-13  1:56     ` David Sharp

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=20101111122645.GA3992@Krystal \
    --to=mathieu.desnoyers@efficios.com \
    --cc=acme@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=dhsharp@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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