Re: profile_tick not called anymore?

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

 



On Mon, 26 Mar 2007 16:07:51 +0200 Ingo Molnar <mingo@xxxxxxx> wrote:

> 
> * Sébastien Dugué <sebastien.dugue@xxxxxxxx> wrote:
> 
> >   I see that the calls to profile_tick() have been commented out in 
> > the different timer handlers. Why is this so?
> > 
> >   The only remaining place calling profile_tick() (well, in fact 
> > __profile_tick()) is the NMI watchdog ticker, but I don't enable it on 
> > my box.
> 
> i'm using nmi_watchdog=2 to do profiling - if it's NMI-driven then the 
> readprofile results are alot more informative.
> 

  Thanks Ingo,

  but then I have to explicitly enable it.

  Are there any drawbacks to uncommenting those calls to profile_tick() in
tick_periodic(), tick_nohz_handler() and tick_sched_timer()?

  The reason I ask is that systemtap scripts using the profile probe don't
work on an RT kernel unless nmi_watchdog is set.

  Thanks,

  Sébastien.
-
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