From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757442AbZBZBlr (ORCPT ); Wed, 25 Feb 2009 20:41:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753121AbZBZBli (ORCPT ); Wed, 25 Feb 2009 20:41:38 -0500 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.125]:49002 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752668AbZBZBlh (ORCPT ); Wed, 25 Feb 2009 20:41:37 -0500 Date: Wed, 25 Feb 2009 20:41:33 -0500 (EST) From: Steven Rostedt X-X-Sender: rostedt@gandalf.stny.rr.com To: Mathieu Desnoyers cc: Frederic Weisbecker , Jason Baron , Masami Hiramatsu , KOSAKI Motohiro , Peter Zijlstra , "Frank Ch. Eigler" , mingo@elte.hu, linux-kernel@vger.kernel.org, acme@ghostprotocols.net, Dominique Toupin Subject: Re: [PATCH] new irq tracer In-Reply-To: <20090225231325.GB21928@Krystal> Message-ID: References: <1234995035.4799.14.camel@laptop> <20090220195236.GB3104@redhat.com> <20090222123543.359C.A69D9226@jp.fujitsu.com> <49A5765C.2020001@redhat.com> <20090225165747.GC3123@redhat.com> <20090225173412.GA14269@Krystal> <20090225221210.GA20133@Krystal> <20090225222001.GC5838@nowhere> <20090225231325.GB21928@Krystal> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) 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 Wed, 25 Feb 2009, Mathieu Desnoyers wrote: > > > > > > > > Then use the function_graph tracer. > > > > > > > > > > Sadly, the function tracer cannot be enabled on production systems. > > > Therefore it's not a usable solution in the context where I need this. > > > > > > Mathieu > > > > > > Why? > > If this is about the interrupt latency caused by stop_machine, I still don't understand. > > This latency happens before the tracing (function filter which use patching), not during > > tracing. > > > > Given this scenario : > > A telecommunication system runs, but the client notices something wrong. > They call their service provider. The provider enables tracing > _remotely_ on the _production system_ while it's _active in the field_. > > Bam, those few milliseconds interrupt latencies become unacceptable. > > Hopefully this scenario makes the use-case clearer. The problem is not > that interrupt latencies would occur while tracing is on, but rather > that it would happen on a running production system when switching > tracing on. This is what is totally unacceptable for this use-case. > > For more details about such requirements, I'm CCing Dominique Toupin > from Ericsson who I'm sure would be happy to give more details about > this if needed. Hmm, so this system in the field is running Linux with the Real-Time Patch? Because if it isn't it will suffer from millisecond latencies in normal operation. -- Steve