From: Christoph Hellwig <hch@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>, Greg KH <greg@kroah.com>,
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: Sun, 25 Oct 2009 00:05:03 -0400 [thread overview]
Message-ID: <20091025040503.GA15781@infradead.org> (raw)
In-Reply-To: <1256303528.20866.822.camel@gandalf.stny.rr.com>
On Fri, Oct 23, 2009 at 09:12:08AM -0400, Steven Rostedt wrote:
> Note, I wasn't talking about tie down the pretty-print formats. But we
> need to have a standard way to change them.
Which means to tie down it I think. Once we do have a good enough
format those bits need to be locked down, with a way for adding new
attributes (either entirely new or better replacmeents for existing
ones with leaving the old ones in place for existing userspace).
In addition to the format description people have also asked for ABI
tracepoints which would lock down the actual trace format in the
the same way (only addition of new fields without removing or changing
existing ones). For this to be actually useful some trace buffer
also needs to be exposed in an ABI-stable (that is non-debugfs way).
next prev parent reply other threads:[~2009-10-25 4:05 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 [this message]
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=20091025040503.GA15781@infradead.org \
--to=hch@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=greg@kroah.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