Re: Enabling function trace on call during module init

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 6 Sep 2013 20:55:54 -0700
Venkat Subbiah <venkat.mlist@xxxxxxxxx> wrote:

> Hello,
> 
> Would like to be able to trace function calls executed during the
> initialization of the kernel module. Is that possible?
> 

Well, yes and no, and it depends ;-)


You wont be able to trace any function that is annotated with "__init",
or even "__exit". That's because the init section does not have a
standard way of cleaning them up (for boot, modules are different, but
are still affected by it).

As ftrace modifies code, and it modifies locations of functions, it can
not safely modify code that suddenly disappeared without it knowing it,
otherwise you may end up with broken NIC cards.

Note, I do plan on adding code that will fix this in the future, but
today, unfortunately, we don't have it.

For functions that are not marked by __init, they will be traced. If
you trace all functions, they will be traced when the module is loaded.
This may not help you either, because by tracing all functions, you
will probably lose the data you want due to overflow of the buffers.

This too may change in the future, but currently we don't have it :-/

-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [RT Stable]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux