tracing module init functions

Frank Ch. Eigler fche@redhat.com
Fri May 9 19:59:00 GMT 2008


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



More information about the Systemtap mailing list