[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100304213725.GA8169@nowhere>
Date: Thu, 4 Mar 2010 22:37:28 +0100
From: Frederic Weisbecker <fweisbec@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Ingo Molnar <mingo@...e.hu>, Peter Zijlstra <peterz@...radead.org>,
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
On Thu, Mar 04, 2010 at 04:30:38PM -0500, Steven Rostedt wrote:
> On Thu, 2010-03-04 at 22:17 +0100, Ingo Molnar wrote:
> > * Steven Rostedt <rostedt@...dmis.org> wrote:
> >
>
> > 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/.
>
> I was talking about the files in the events directory:
>
> events/sched/sched_switch/{id,format,enable,filter}
>
>
> Seems only the format file should go in, and perhaps the id.
>
> I can keep the debug/tracing/events/* as is too, where the format and id
> just call the same routines that the eventfs calls, but add the enable
> and filter to be specific to ftrace.
The /debug/tracing/events could contain symlinks for the format
files so that the rest can stay there.
--
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