From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Greg KH <greg@kroah.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC] tracefs
Date: Fri, 23 Oct 2009 07:35:30 +0200 [thread overview]
Message-ID: <20091023053530.GB24359@elte.hu> (raw)
In-Reply-To: <1256260230.20866.816.camel@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.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
next prev parent reply other threads:[~2009-10-23 5:35 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 [this message]
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
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=20091023053530.GB24359@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