Messages in this thread | | | Date | Tue, 7 Jan 2014 21:07:19 -0500 | From | Steven Rostedt <> | Subject | Re: [RFC][PATCH] tracing: Show available event triggers when no trigger is set |
| |
On Tue, 07 Jan 2014 17:34:56 -0600 Tom Zanussi <tom.zanussi@linux.intel.com> wrote:
> Nice idea - very helpful and makes use of that 'unused space'. ;-)
I came up with it when I was writing my tests against the event triggers, and didn't know what triggers I had, and realized there was no easy way to figure it out.
> > Even better might be printing the full event formats and examples as in > tracing/README, but that would probably mean adding a new event-specific > description function to event_command, and it might get unwieldy with > too many events. Just a thought...
I had that same thought, but then thought against it. It would make things too complicated, and that's what text documentation is for. Or we can even add it to the tracing/README too.
-- Steve
| |