linux-kernel - Re: [PATCH 1/2] tracing, boottrace: Move include/trace/boot.h to include/linux/boottrace.h

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]

Date:	Mon, 13 Apr 2009 19:51:17 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Zhaolei <zhaolei@...fujitsu.com>,
	Tom Zanussi <tzanussi@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] tracing, boottrace: Move include/trace/boot.h to
 include/linux/boottrace.h


On Tue, 14 Apr 2009, Ingo Molnar wrote:

> 
> * Steven Rostedt <rostedt@...dmis.org> wrote:
> 
> > On Tue, 14 Apr 2009, Ingo Molnar wrote:
> > > 
> > > The sane thing would be to put event headers into 
> > > include/trace/events/ and put more generic/utility headers into 
> > > include/trace/.
> > > 
> > > Reserving a full subdirectory for one singular purpose is a needless 
> > > waste of a nice (and unique) name-space resource.
> > 
> > That's fine with me too. I just want the trace points to be easily 
> > seen. But by making a sub directory, wont we need to have all 
> > users of tracepoints do something like:
> > 
> > #include <trace/events/sched.h>
> > 
> > That might be fine too.
> 
> Yes - it would allow the dropping of the annoyingly repetitive 
> _event string from those definition files as well?

The coming patches for modules already does that ;-)

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