[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4B17E337.8070301@redhat.com>
Date: Thu, 03 Dec 2009 11:11:35 -0500
From: Masami Hiramatsu <mhiramat@...hat.com>
To: rostedt@...dmis.org
CC: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
akpm@...ux-foundation.org, Ingo Molnar <mingo@...e.hu>,
mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org,
randy.dunlap@...cle.com, wcohen@...hat.com, fweisbec@...il.com,
tglx@...utronix.de, jbaron@...hat.com,
linux-tip-commits@...r.kernel.org, Christoph Hellwig <hch@....de>
Subject: Re: trace/events: DECLARE vs DEFINE semantic
Steven Rostedt wrote:
> On Thu, 2009-12-03 at 10:31 -0500, Masami Hiramatsu wrote:
>> Steven Rostedt wrote:
>
>>>> Would you mean putting those headers in sub-system's directory?
>>>> (e.g. fs/ext4/)
>>>> In that case, a problem will happen when user want to hook those
>>>> tracepoint from their module, because it is hard to find those
>>>> local headers.
>>>
>>> Why? Modules usually do have their own headers in their sub system.
>>
>> Module's local headers usually uses only from itself. Other modules
>> may not touch it. However, AFAIK, event definitions must be referred
>> by event consumer which is another module. IOW, those local headers
>> will not be included in kernel-headers/kernel-devel package :-(
>
> I'm a little confused. Who is the event consumer? The trace point user?
> The one that hooks into the tracepoint?
Ah, I meant the tracepoint user module, not the ftrace event consumer.
Thank you,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division
e-mail: mhiramat@...hat.com
--
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