Messages in this thread | | | From | Nick Piggin <> | Subject | Re: [PATCH 2/4] tracing: add event trace infrastructure | Date | Wed, 25 Feb 2009 15:24:35 +1100 |
| |
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@goodmis.org> wrote: > > > From: Steven Rostedt <srostedt@redhat.com> > > > > > > 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? ;)
| |