Re: [PATCH] tracing/filters: allow event filters to be set only whennot tracing

From: Steven Rostedt
Date: Mon Apr 06 2009 - 20:34:38 EST




On Mon, 6 Apr 2009, Paul E. McKenney wrote:
>
> Hmmm... Do the start_critical_timings() and stop_critical_timings()
> functions have anything to do with ftrace()?

Yep.

>
> It does not look like I can just bury RCU-idle controls in these
> functions, given that they are also invoked around call_console_drivers(),
> but if all the idle loops are surrounded by stop_critical_timings() and
> start_critical_timings(), that would ease location of all the idle
> loops. ;-)

They are for the irqsoff tracer. Several archs will disable interrupts and
call an assembly "halt" type instruction that can be woken up by
interrupts. But this skips the irqs off check, and we end up with irqsoff
showing the idle loop with huge interrupts off latencies.

I'm not sure they are included in all archs. They may be.

-- Steve

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/