Re: Enabling function trace on call during module init

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

 



On Fri, 11 Oct 2013 12:15:31 +0200
Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx> wrote:

> * Steven Rostedt | 2013-09-07 20:48:11 [-0400]:
> 
> >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).
> 
> Is this even required / wanted? Usually the module just hooks itself
> into subsystem like pci_register_driver() and is usually not
> interresting. The interresting part starts from ->probe() (I think) and
> this is captured, right?

Only if the ->probe() is not marked __init

There's a white list of sections that the function tracer traces. See
is_mcounted_section_name() in scripts/recordmcount.c.

-- 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