Messages in this thread | | | Date | Wed, 25 Feb 2009 09:10:07 -0500 (EST) | From | Steven Rostedt <> | Subject | Re: [PATCH 2/4] tracing: add event trace infrastructure |
| |
On Wed, 25 Feb 2009, Theodore Tso wrote:
> On Tue, Feb 24, 2009 at 07:45:48PM -0800, Andrew Morton wrote: > > echo sched_wakeup > /debug/tracing/set_event > > echo sched_wakeup > /debug/tracing/clear_event > > echo 1 > /debug/tracing/clear_all_events > > >From a usability point of view, I'd prefer this as well. It's only > two extra files, but it means that filenames in /deb/tracing is > self-documenting, which is a good thing. Otherwise, it's really not > obvious that "echo !event > /debug/tracing/set_event" will disable the > event, and it's *especially* not obvious "echo > /debug/tracing/set_event" > will disable all events. > > It's also a tad bit too easy to typo "echo > /debug/tracing/set_event" > by editing command history, and hitting return a bit too soon after > clearing out the previous event name but before you manage to type the > new event name.
OK, then I guess I can add a clear_event file. And to clear all events simply do:
# cat set_event > clear_event
-- Steve
| |