From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753914AbYI0T3A (ORCPT ); Sat, 27 Sep 2008 15:29:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752595AbYI0T2v (ORCPT ); Sat, 27 Sep 2008 15:28:51 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.122]:55365 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752355AbYI0T2u (ORCPT ); Sat, 27 Sep 2008 15:28:50 -0400 Date: Sat, 27 Sep 2008 15:28:48 -0400 (EDT) From: Steven Rostedt X-X-Sender: rostedt@gandalf.stny.rr.com To: Ingo Molnar cc: Steven Noonan , "Luis R. Rodriguez" , Luis Rodriguez , "ath9k-devel@lists.ath9k.org" , linux-wireless , LKML Subject: Re: [ath9k-devel] ath9k: massive unexplained latency in 2.6.27 (rc5, rc6, probably others) In-Reply-To: <20080927192019.GE18619@elte.hu> Message-ID: References: <43e72e890809181508w5232a14ewbf2bf18fe90a92d5@mail.gmail.com> <43e72e890809181610h3a7729d8s4c8484d97b21932e@mail.gmail.com> <20080919030125.GG7408@tesla> <20080919081733.GC19491@elte.hu> <20080919083208.GA15730@elte.hu> <20080927192019.GE18619@elte.hu> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 27 Sep 2008, Ingo Molnar wrote: > > * Steven Rostedt 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. OK, on Monday, as I work on getting ftrace to use the ring buffer, I'll also look to see which features are only in -rt that need to go to tip. -- Steve