[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48612879.5090809@redhat.com>
Date: Tue, 24 Jun 2008 13:01:45 -0400
From: Masami Hiramatsu <mhiramat@...hat.com>
To: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
CC: Takashi Nishiie <t-nishiie@...css.fujitsu.com>,
"'Alexey Dobriyan'" <adobriyan@...il.com>,
"'Mathieu Desnoyers'" <mathieu.desnoyers@...ymtl.ca>,
"'Peter Zijlstra'" <peterz@...radead.org>,
"'Steven Rostedt'" <rostedt@...dmis.org>,
"'Frank Ch. Eigler'" <fche@...hat.com>,
"'Ingo Molnar'" <mingo@...e.hu>,
"'LKML'" <linux-kernel@...r.kernel.org>,
"'systemtap-ml'" <systemtap@...rces.redhat.com>,
"'Hideo AOKI'" <haoki@...hat.com>
Subject: Re: [RFC] Tracepoint proposal
KOSAKI Motohiro wrote:
>> Tracepoint
>> - stored in a section
>> - dynamic activation
>> - no message
>> - export kernel structure
>> - arguments depending on points
>> - high frequently called
>> - no module support (kernel use only)
>
> Why Shouldn't kernel module use tracepoint?
> technical problem? or any plicy exist?
Good question, I think we don't want to export so much
kernel internal structures. Since tracepoint tend to export
raw kernel structure to user module, I thought it might be
better not to export its interface to modules.
However, I thought that again, and knew what Peter worried was
about marker which exports marker list to user space.
So, the issue is exporting internal structures to user space,
not to modules. Thus, I think it can support modules also.
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