[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100304211741.GB3643@elte.hu>
Date: Thu, 4 Mar 2010 22:17:41 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Paul Mackerras <paulus@...ba.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Greg KH <greg@...ah.com>
Subject: Re: [RFC][PATCH 2/3] perf: Take a hot regs snapshot for trace events
* Steven Rostedt <rostedt@...dmis.org> wrote:
> On Thu, 2010-03-04 at 16:36 +0100, Ingo Molnar wrote:
>
> > > This should be done anyway. But it would also let you decouple ftrace trace
> > > events from perf trace events but still let the two use the same trace
> > > points.
> >
> > I think the main thing would be to have a decoupled /eventfs - basically
> > /debug/tracing/events/ moved to "/eventfs" or maybe to "/proc/events/". This
> > would make them available more widely, and in a standardized way.
>
> I know Greg once proposed a /tracefs directory. I don't really care how
> things work as long as we don't lose functionality. Perhaps we should have a
> standard tracefs dir, and have:
No, we want to decouple it from 'tracing'. It's events, not tracing. Events
are more broader, they can be used for RAS, profiling, counting, etc. - not
just tracing.
Furthermore, we only want /debug/tracing/events really, not the various
dynamic ftrace controls - those could remain in /debug/tracing/.
Thanks,
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