Re: [PATCH 1/3] printk: Release console_sem after logbuf_lock

Ingo Molnar
2011-06-10T12:34:46Z

* Peter Zijlstra <peterz@infradead.org> wrote:

> thinking that that would have my printk stmts appear on both the
> fbcon as well as the serial line. But they fail to appear on the
> latency tracer (current max was 165us waking an idle cpu).

Have you removed this bit:

spin_unlock(&logbuf_lock);
stop_critical_timings(); /* don't trace print latency */
call_console_drivers(_con_start, _log_end);
start_critical_timings();
local_irq_restore(flags);

which hides the latencies from the latency tracer?

Thanks,

Ingo