linux-kernel - Re: [PATCH 1/5] tracing/events: enable code with EVENT_TRACING not EVENT

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] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.0904181017010.1016@gandalf.stny.rr.com>
Date:	Sat, 18 Apr 2009 10:18:52 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 1/5] tracing/events: enable code with EVENT_TRACING not
 EVENT_TRACER


On Sat, 18 Apr 2009, Ingo Molnar wrote:

> 
> * Steven Rostedt <rostedt@...dmis.org> wrote:
> 
> > -#ifdef CONFIG_EVENT_TRACER
> > +#ifdef CONFIG_EVENT_TRACING
> 
> Hm, my crystal ball predicts many such incidents in future years to 
> come.
> 
> This:
> 
>   s/CONFIG_EVENT_TRACER/CONFIG_EVENT_TRACER_PLUGIN
> 
> might help. Or not.

The problem is that a plugin is defined (by me anyway) as something in the 
"available_tracers" file. The event tracer does not qualify as one. But I 
see the confusion with the current naming.

What about:

	s/CONFIG_EVENT_TRACER/CONFIG_ENABLE_EVENT_TRACING/

It pretty much says what it does.

??

-- 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/