linux-kernel - Re: [RFC] tracefs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091023102939.GE19169@elte.hu>
Date:	Fri, 23 Oct 2009 12:29:39 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Greg KH <greg@...ah.com>, Steven Rostedt <rostedt@...dmis.org>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [RFC] tracefs


* Frederic Weisbecker <fweisbec@...il.com> wrote:

> On Fri, Oct 23, 2009 at 07:32:37AM +0200, Ingo Molnar wrote:
> > 
> > * Greg KH <greg@...ah.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 ;-).
> > 
> > We want a _very_ careful exporting of certain pieces of information 
> > that helps syscall-exposed perf events bits, and to improve the 
> > quality of interfaces while we do that.
> > 
> > 	Ingo
> 
> 
> I guess the first bits that need to be exported are the 
> TRACE_EVENT_ABI. But even before that, we need to ensure we have a 
> final version of the trace events description.

Yeah, exactly. Once we pin them down they'll be with us for a very long 
time.

	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/