linux-kernel - Re: [RFC][PATCH] tracing: Show available event triggers when no trigger is set

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140107210719.3bc0af29@gandalf.local.home>
Date:	Tue, 7 Jan 2014 21:07:19 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Tom Zanussi <tom.zanussi@...ux.intel.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
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@...ux.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

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