This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [ltt-dev] [PATCH] tracepoints: Generate Module.tracepoints file
- From: KOSAKI Motohiro <kosaki dot motohiro at jp dot fujitsu dot com>
- To: fche at redhat dot com (Frank Ch. Eigler)
- Cc: kosaki dot motohiro at jp dot fujitsu dot com, Jan Blunck <jblunck at suse dot de>, ltt-dev Mailing List <ltt-dev at lists dot casi dot polymtl dot ca>, Mathieu Desnoyers <mathieu dot desnoyers at polymtl dot ca>, systemtap at sourceware dot org
- Date: Wed, 24 Sep 2008 03:07:50 +0900 (JST)
- Subject: Re: [ltt-dev] [PATCH] tracepoints: Generate Module.tracepoints file
- References: <20080918150841.GW18393@bolzano.suse.de> <y0mzlm0mbo6.fsf@ton.toronto.redhat.com>
Hi
> Jan Blunck <jblunck@suse.de> writes:
>
> > This adds support to generate the Module.tracepoints file by modpost. This
> > can be read by tools like SystemTap very similar to the Module.markers file.
> > [...]
>
> For systemtap, the problem with tracepoints is not so much knowing the
> list of them, but knowing how to dynamically interface to them. In
> particular, the parameter type signatures are a problem because they
> can be general C type decls, which are hard just to parse.
systemtap want to one systemtap binary support multiple kernel versions?
Otherwise *.h file works enough, I think.
So, I think you should talk about systemtap requirement.
Thanks!