From: Greg KH <greg@kroah.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
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: Tue, 27 Oct 2009 18:06:47 -0700 [thread overview]
Message-ID: <20091028010647.GB14956@kroah.com> (raw)
In-Reply-To: <20091023053237.GA24359@elte.hu>
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 ;-).
Ok, I'll drop this. There was some cleanups I found, I'll pick those
out and send them on. What tree should I base off of to send cleanup
patches to?
thanks,
greg k-h
next prev parent reply other threads:[~2009-10-28 1:06 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
2009-10-23 13:12 ` Steven Rostedt
2009-10-25 4:05 ` Christoph Hellwig
2009-10-28 1:06 ` Greg KH [this message]
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=20091028010647.GB14956@kroah.com \
--to=greg@kroah.com \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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