Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750739AbWABOO7 (ORCPT ); Mon, 2 Jan 2006 09:14:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750744AbWABOO7 (ORCPT ); Mon, 2 Jan 2006 09:14:59 -0500 Received: from gateway-1237.mvista.com ([12.44.186.158]:31218 "EHLO hermes.mvista.com") by vger.kernel.org with ESMTP id S1750739AbWABOO6 (ORCPT ); Mon, 2 Jan 2006 09:14:58 -0500 Subject: RE: Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1) From: Daniel Walker To: kus Kusche Klaus Cc: Ingo Molnar , Lee Revell , linux-kernel In-Reply-To: References: Content-Type: text/plain Date: Mon, 02 Jan 2006 06:14:55 -0800 Message-Id: <1136211295.22548.7.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 797 Lines: 18 On Mon, 2006-01-02 at 08:57 +0100, kus Kusche Klaus wrote: > > -0 0D... 1us+: preempt_schedule_irq (svc_preempt) > -0 0.... 5us!: default_idle (cpu_idle) > -0 0D..1 8700us+: asm_do_IRQ (c021da48 1a 0) Your trace appears to be showing an actual latency of 300us . The trace starts at 8700us . The default_idle line above is showing interrupts are enable, and preemption is enabled . So the tracing code really should be ignoring the default_idle line since there is no reason to be tracing. Daniel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/