On Wed, 08 Jan 2014 16:50:47 +0900
Namhyung Kim wrote:
> [SNIP]
> > + if (v == SHOW_AVAILABLE_TRIGGERS) {
> > + seq_puts(m, "# Available triggers:\n");
> > + seq_putc(m, '#');
> > + mutex_lock(&trigger_cmd_mutex);
> > + list_for_each_entry(p, &trigger_com
Hi Steve,
On Tue, 7 Jan 2014 10:35:48 -0500, Steven Rostedt wrote:
> Currently there's no way to know what triggers exist on a kernel without
> looking at the source of the kernel or randomly trying out triggers.
> Instead of creating another file in the debugfs system, simply show
> what availabl
On Tue, 07 Jan 2014 17:34:56 -0600
Tom Zanussi 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.
>
> E
On Tue, 2014-01-07 at 10:35 -0500, Steven Rostedt wrote:
> Currently there's no way to know what triggers exist on a kernel without
> looking at the source of the kernel or randomly trying out triggers.
> Instead of creating another file in the debugfs system, simply show
> what available triggers
Currently there's no way to know what triggers exist on a kernel without
looking at the source of the kernel or randomly trying out triggers.
Instead of creating another file in the debugfs system, simply show
what available triggers are there when cat'ing the trigger file when
it has no events:
5 matches
Mail list logo
