From mboxrd@z Thu Jan  1 00:00:00 1970
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Date: Thu, 15 Jan 2009 10:18:55 -0500
Subject: [ltt-dev] Interpreting tracing results
In-Reply-To: <1E65288790442545B413D69F2A8D27DE045EBBC4@ERLD164A.ww004.siemens.net>
References: <1E65288790442545B413D69F2A8D27DE045EBBC4@ERLD164A.ww004.siemens.net>
Message-ID: <20090115151855.GA27345@Krystal>

* Akyurek, Ali (EXT) (ali.akyurek.ext at siemens.com) wrote:
> 
> Hi all,
> 
> In my arm machine, context switching takes 1220 or 1221 nanoseconds. 
> i thought this time as (start of sched_schedule - start of
> whatever_previous_event), Actually that is the time between different
> PID values in rows.am i right?
> 
> and
> 
> Handling of interrupts (i take only the top handlers, not soft ones.)
> takes 2441 nanoseconds.
> i thought this time as (end of irq_exit - start of irq_entry), am i
> right?
> 
> Why are these values multiple of 1220 nanoseconds? What is related to? 
> 

Hi,

LTTng uses the generic trace clock for ARM by default. See
include/asm-generic/trace-clock.h.

This clock has only the precision of HZ frequency, and I use an atomic
counter in the LSBs to keep the events ordered.

Please have a look at the ARM-related messages in the past 2 weeks for
implementations of sub-arch specific clock sources for ARM. I will
integrate this kind of work soon after making sure it's smp-safe when it
needs to.

Mathieu

> Thanks all.
> 
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68