Messages in this thread | | | Date | Thu, 29 Oct 2009 09:04:10 +0100 | From | Ingo Molnar <> | Subject | Re: [RFC] tracefs |
| |
* Greg KH <greg@kroah.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 ;-). > > 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?
The tip of the tracing tree is in tip:tracing/core, you can find it at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git tracing/core
Thanks,
Ingo
| |