Re: [PATCH 2/4] tracing: add event trace infrastructure

[Nick Piggin]

On Wednesday 25 February 2009 15:08:56 Steven Rostedt wrote:
> On Tue, 24 Feb 2009, Andrew Morton wrote:
> > On Tue, 24 Feb 2009 21:56:10 -0500 Steven Rostedt <rostedt@xxxxxxxxxxx> 
wrote:
> > > From: Steven Rostedt <srostedt@xxxxxxxxxx>
> > >
> > > This patch creates the event tracing infrastructure of ftrace.
> > > It will create the files:
> > >
> > >  /debug/tracing/available_events
> > >  /debug/tracing/set_event
> > >
> > > The available_events will list the trace points that have been
> > > registered with the event tracer.
> > >
> > > set_events will allow the user to enable or disable an event hook.
> > >
> > > example:
> > >
> > >  # echo sched_wakeup > /debug/tracing/set_event
> > >
> > > Will enable the sched_wakeup event (if it is registered).
> > >
> > >  # echo "!sched_wakeup" >> /debug/tracing/set_event
> > >
> > > Will disable the sched_wakeup event (and only that event).
> >
> > Why not
> >
> > echo sched_wakeup > /debug/tracing/set_event
> > echo sched_wakeup > /debug/tracing/clear_event
>
> I'm trying to keep the number of files in /debug/tracing down.

Why? Andrew's proposal is much cleaner. (what is the !sched_wakeup
event? An event you get when the scheduler does not wake up a task? ;)


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/