public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Greg KH <greg@kroah.com>, Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [RFC] tracefs
Date: Fri, 23 Oct 2009 12:29:39 +0200	[thread overview]
Message-ID: <20091023102939.GE19169@elte.hu> (raw)
In-Reply-To: <20091023093838.GA4939@nowhere>


* Frederic Weisbecker <fweisbec@gmail.com> wrote:

> On Fri, Oct 23, 2009 at 07:32:37AM +0200, Ingo Molnar wrote:
> > 
> > * Greg KH <greg@kroah.com> wrote:
> > 
> > > Hi all,
> > > 
> > > At LinuxCon this year, Steven and I talked about moving the 
> > > debugfs usage in the tracing core to a stand-alone filesystem to 
> > > give the ability to start to lock down the api so that people an 
> > > count on what is going on in the tracing userspace interface.
> > 
> > What we want to move out initially (and i talked to Steve and 
> > Frederic about that a few weeks ago) is the event description bits - 
> > the format stuff in /debug/tracing/events/ - but definitely not all 
> > the other, rather messy and ad-hoc APIs.
> > 
> > _No way_ do we want to tie down the pretty-printing ftrace details 
> > as an ABI. We promised that when ftrace went upstream and all the 
> > details are way too messy to be exposed in an ABI alike matter (and 
> > yes, consider this a NAK Steve ;-).
> > 
> > We want a _very_ careful exporting of certain pieces of information 
> > that helps syscall-exposed perf events bits, and to improve the 
> > quality of interfaces while we do that.
> > 
> > 	Ingo
> 
> 
> I guess the first bits that need to be exported are the 
> TRACE_EVENT_ABI. But even before that, we need to ensure we have a 
> final version of the trace events description.

Yeah, exactly. Once we pin them down they'll be with us for a very long 
time.

	Ingo

  reply	other threads:[~2009-10-23 10:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23  0:49 [RFC] tracefs Greg KH
2009-10-23  1:10 ` Steven Rostedt
2009-10-23  4:27   ` Greg KH
2009-10-23  5:35   ` Ingo Molnar
2009-10-23  5:32 ` Ingo Molnar
2009-10-23  9:38   ` Frederic Weisbecker
2009-10-23 10:29     ` Ingo Molnar [this message]
2009-10-23 13:12   ` Steven Rostedt
2009-10-25  4:05     ` Christoph Hellwig
2009-10-28  1:06   ` Greg KH
2009-10-29  8:04     ` 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=20091023102939.GE19169@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=fweisbec@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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