[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0904062029440.24008@gandalf.stny.rr.com>
Date: Mon, 6 Apr 2009 20:30:11 -0400 (EDT)
From: Steven Rostedt <rostedt@...dmis.org>
To: Frederic Weisbecker <fweisbec@...il.com>
cc: Tony Luck <tony.luck@...el.com>, Ingo Molnar <mingo@...e.hu>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>, tglx@...utronix.de,
Jason Baron <jbaron@...hat.com>,
"Frank Ch. Eigler" <fche@...hat.com>,
Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Lai Jiangshan <laijs@...fujitsu.com>,
Jiaying Zhang <jiayingz@...gle.com>,
Michael Rubin <mrubin@...gle.com>,
Martin Bligh <mbligh@...gle.com>,
Michael Davidson <md@...gle.com>
Subject: Re: [PATCH 1/2 v2] tracing/syscalls: core infrastructure for syscalls
tracing
On Tue, 7 Apr 2009, Frederic Weisbecker wrote:
> >
> > What does syscalls.h really need to pull in at this point ... is there
> > a way for it to get it without pulling in so much extra stuff?
>
>
> Ah, I see. I wondered somewhat when I included ftrace.h from syscall.h,
> I didn't know why it stressed me but now I understand :-)
>
> Though this is weird that both ia32 and ia64 definitions are allowed to be
> included like that.
>
> Anyway, I will put the syscalls tracing headers to a separate file to fix
> that, thanks for reporting this!
Yeah, probably just separate out what is needed into a file called
syscall_trace.h ?
-- 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/
Powered by blists - more mailing lists