[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091023053530.GB24359@elte.hu>
Date: Fri, 23 Oct 2009 07:35:30 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Greg KH <greg@...ah.com>, Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC] tracefs
* Steven Rostedt <rostedt@...dmis.org> wrote:
> On Thu, 2009-10-22 at 17:49 -0700, Greg KH 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.
> >
> > So, on the flight to Tokyo for the kernel summit, I wrote up tracefs.
> > Here's the first very rough cut at it below. I've run it here on my
> > laptop, and all seems well, but I do have a few questions:
> > - I've made the mount point be /sys/kernel/trace/ Is that ok? Should
> > it be /sys/kernel/tracing/? Or something else? You get to pick the
> > mount point now, so I don't want to hear any more grumblings about
> > the location in the future :)
>
> /trace
>
> (rostedt hides)
No, what we want is either /sys/events/ or /proc/events/ alike place to
expose event logging formats (i.e. the /debug/tracing/events/ details).
Those are clean enough to be exposed as an ABI - and it would be a good
point to start.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists