From: Daniel Walker <dwalker@mvista.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Lee Revell <rlrevell@joe-job.com>,
kus Kusche Klaus <kus@keba.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1)
Date: Fri, 30 Dec 2005 05:07:25 -0800 [thread overview]
Message-ID: <1135948046.32431.0.camel@localhost.localdomain> (raw)
In-Reply-To: <20051230074424.GB25637@elte.hu>
On Fri, 2005-12-30 at 08:44 +0100, Ingo Molnar wrote:
> there seem to be leaked preempt counts:
>
> <idle>-0 0.n.1 8974us : touch_critical_timing (cpu_idle)
>
> we should never have preemption disabled in cpu_idle(). To debug leaked
> preemption counts, enable CONFIG_DEBUG_PREEMPT.
ARM does disable preemption in cpu_idle() .
Daniel
next prev parent reply other threads:[~2005-12-30 13:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-29 15:08 Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1) 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-30 6:35 kus Kusche Klaus
2005-12-30 7:42 Kai Geek
2005-12-30 18:46 ` Lee Revell
2005-12-30 8:02 kus Kusche Klaus
2005-12-30 10:35 kus Kusche Klaus
2005-12-30 10:59 kus Kusche Klaus
2005-12-30 11:18 kus Kusche Klaus
2005-12-30 12:40 kus Kusche Klaus
2005-12-30 13:35 ` Daniel Walker
2006-01-02 7:57 kus Kusche Klaus
2006-01-02 14:14 ` Daniel Walker
2006-01-02 14:39 kus Kusche Klaus
2006-01-02 14:44 ` Daniel Walker
2006-01-02 14:55 kus Kusche Klaus
2006-01-02 15:36 ` Daniel Walker
2006-01-02 16:07 ` Daniel Walker
2006-01-03 7:27 kus Kusche Klaus
2006-01-03 8:00 kus Kusche Klaus
2006-01-03 14:16 ` Daniel Walker
2006-01-03 14:57 kus Kusche Klaus
2006-01-03 15:01 ` Daniel Walker
2006-01-03 15:40 kus Kusche Klaus
2006-01-04 9:28 kus Kusche Klaus
2006-01-05 14:30 ` Daniel Walker
2006-01-05 15:32 kus Kusche Klaus
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=1135948046.32431.0.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox