All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 05 Jan 2006 06:30:42 -0800	[thread overview]
Message-ID: <1136471443.31011.1.camel@localhost.localdomain> (raw)
In-Reply-To: <AAD6DA242BC63C488511C611BD51F367323316@MAILIT.keba.co.at>

On Wed, 2006-01-04 at 10:28 +0100, kus Kusche Klaus wrote:
> > From: Daniel Walker
> > Ok, yet another patch. This one uses the correct lowlevel calls, and I
> > fixed the call ordering.
> 
> Hmm, I have no deep knowledge of ARM assembler programming,
> but your patch branches to a C subroutine without setting up a
> return address in the lr register.
> 
> Hence, the return in trace_irqs_... jumps to god-knows-where,
> but not back to the next instruction.
> 
> As a wild guess, I replaced the "b trace_irqs_..." with
> "bl trace_irqs_...".

Ok .

> With this change, the kernel boots fine, but the system seems to go
> into an infinite loop as soon as the first usermode processes start.
> Most likely, my change messes up the lr register of some surrounding
> context.

That's odd. Do you have an OOPS, or is it just a silent hang?


Daniel


  reply	other threads:[~2006-01-05 14:30 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04  9:28 Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1) kus Kusche Klaus
2006-01-05 14:30 ` Daniel Walker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-05 15:32 kus Kusche Klaus
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 14:39 kus Kusche Klaus
2006-01-02 14:44 ` 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=1136471443.31011.1.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.