Re: [ath9k-devel] ath9k: massive unexplained latency in 2.6.27(rc5, rc6, probably others)

From: Ingo Molnar
Date: Sat Sep 27 2008 - 15:20:52 EST



* Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:

>
> I hate trips where my email box becomes filled. I skip over a lot of
> emails that I should not have.
>
> On Fri, 19 Sep 2008, Ingo Molnar wrote:
> >
> > What is needed is to set kernel/trace/trace.c's tracing_disabled
> > variable to 0. I've Cc:-ed Steve Rostedt - Steve, why is there no easy
> > ad-hoc way to trigger a stop-tracing event without elaborate changes?
>
> I think I added a way to do this. Hmm, I think it was in -rt that I added
> it, and have not gotten around to sending you the updates.
>
> Yes, we need an easy way to disable the tracer. I think we have
> ftrace_disable() function. Perhaps that only disables tracing that
> checks the tracing_disabled variable.

we have kill_ftrace(), but that will permanently zap it.

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