From: Daniel Walker <dwalker@mvista.com>
To: kus Kusche Klaus <kus@keba.com>
Cc: Ingo Molnar <mingo@elte.hu>, Lee Revell <rlrevell@joe-job.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: RE: Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1)
Date: Mon, 02 Jan 2006 06:44:07 -0800 [thread overview]
Message-ID: <1136213048.22548.12.camel@localhost.localdomain> (raw)
In-Reply-To: <AAD6DA242BC63C488511C611BD51F36732330F@MAILIT.keba.co.at>
On Mon, 2006-01-02 at 15:39 +0100, kus Kusche Klaus wrote:
> > From: Daniel Walker
> > On Mon, 2006-01-02 at 08:57 +0100, kus Kusche Klaus wrote:
> > > <idle>-0 0D... 1us+: preempt_schedule_irq (svc_preempt)
> > > <idle>-0 0.... 5us!: default_idle (cpu_idle)
> > > <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.
>
> Ok, thanks, fine.
>
> I always thought that the output of the tracer always represents a
> single block of latency (either interrupts or preemption disabled),
> from its beginning to its end.
>
> Does that mean that any line with status "0...." is not dangerous
> at all w.r.t. latency?
The tracing isn't correct on ARM . It shouldn't show a max latency of
8700us when it's only 300us . I'm not saying there isn't a problem.
> If this is the case, then it should not only be excluded from the
> trace listing, but also from the total timings! The trace header says
> that this is a latency of 8964 us, and this also means that any
> latency shorter than that is not recorded by the tracer.
>
> However, if the "real" latency of this trace is only 300 us, there
> are quite likely longer "real" latencies (at least, my own test
> programs strongly indicate that), and I'd like to see their traces
> and get the maximum "real" latency duration in the statistics (the
> interrupt latency histogram is also based on the values in the trace
> and not on the "real" latencies: It has a significant peak around
> 8800 us, and I certainly don't have that many int-off periods of
> 8800 us on my system!).
Right .. I'm still looking into it. ARM is just missing some vital
tracing bits I think .
Daniel
next prev parent reply other threads:[~2006-01-02 14:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 14:39 Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1) kus Kusche Klaus
2006-01-02 14:44 ` Daniel Walker [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-05 15:32 kus Kusche Klaus
2006-01-04 9:28 kus Kusche Klaus
2006-01-05 14:30 ` Daniel Walker
2006-01-03 15:40 kus Kusche Klaus
2006-01-03 14:57 kus Kusche Klaus
2006-01-03 15:01 ` Daniel Walker
2006-01-03 8:00 kus Kusche Klaus
2006-01-03 14:16 ` Daniel Walker
2006-01-03 7:27 kus Kusche Klaus
2006-01-02 14:55 kus Kusche Klaus
2006-01-02 15:36 ` Daniel Walker
2006-01-02 16:07 ` Daniel Walker
2006-01-02 7:57 kus Kusche Klaus
2006-01-02 14:14 ` Daniel Walker
2005-12-30 12:40 kus Kusche Klaus
2005-12-30 13:35 ` Daniel Walker
2005-12-30 11:18 kus Kusche Klaus
2005-12-30 10:59 kus Kusche Klaus
2005-12-30 10:35 kus Kusche Klaus
2005-12-30 8:02 kus Kusche Klaus
2005-12-30 7:42 Kai Geek
2005-12-30 18:46 ` Lee Revell
2005-12-30 6:35 kus Kusche Klaus
2005-12-29 15:08 kus Kusche Klaus
2005-12-29 18:25 ` Daniel Walker
2005-12-30 7:29 ` Lee Revell
2005-12-30 7:36 ` Ingo Molnar
2005-12-30 7:44 ` Ingo Molnar
2005-12-30 13:07 ` Daniel Walker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1136213048.22548.12.camel@localhost.localdomain \
--to=dwalker@mvista.com \
--cc=kus@keba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.