This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: tracing module init functions
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Paul Larson <pl at us dot ibm dot com>
- Cc: systemtap at sources dot redhat dot com
- Date: Fri, 09 May 2008 13:06:49 -0400
- Subject: Re: tracing module init functions
- References: <1210348111.25473.2.camel@brick.gateway.2wire.net>
Paul Larson <pl@us.ibm.com> writes:
> Is there a way to trace module init functions, and other functions such
> as device probes that happen early when a module comes up? [...]
Not yet. The main reason is that init type functions get unmapped
pretty soon after module loading, so systemtap refuses to put kprobes
into such areas (e.g., bug #1329, #5483). If we were really clever,
we could intercept the module loading process, wrap the init function,
and temporarily insert and remove the kprobes for only the real init
call's duration.
- FChE