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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 26 Sep 2008 21:23:20 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Steven Noonan <steven@...inklabs.net>,
	"Luis R. Rodriguez" <lrodriguez@...eros.com>,
	Luis Rodriguez <Luis.Rodriguez@...eros.com>,
	"ath9k-devel@...ts.ath9k.org" <ath9k-devel@...ts.ath9k.org>,
	linux-wireless <linux-wireless@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [ath9k-devel] ath9k: massive unexplained latency in 2.6.27 (rc5,
 rc6, probably others)

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.

Anyway, I made sure the new ring_buffer code has an easy way to disable 
it.

-- Steve

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