From: Ralf Baechle <ralf@linux-mips.org>
To: Kaz Kylheku <kaz@zeugmasystems.com>
Cc: linux-mips@linux-mips.org
Subject: Re: futex_wake_op deadlock?
Date: Tue, 20 Nov 2007 18:16:19 +0000 [thread overview]
Message-ID: <20071120181619.GA17979@linux-mips.org> (raw)
In-Reply-To: <DDFD17CC94A9BD49A82147DDF7D545C54DCF9F@exchange.ZeugmaSystems.local>
On Tue, Nov 20, 2007 at 10:06:44AM -0800, Kaz Kylheku wrote:
> The problem is I didn't pay enough attention because I didn't suspect it
> enough.
>
> I was misled by the backtrace address in the soft lockup dump, which
> points to one instruction /before/ the ll instruction. So I thought that
> the lockup is somewhere outside of that loop, right?
>
> Does the backward branch on MIPS set up the instruction pointer in such
> a way that if an interrupt goes off, it can be pointing to the previous
> instruction? I thought about that possibility.
The EPC will always point to the instruction which caused the exception
with the one special case where an instruction in a branch delay slot
was causing the exception. If that's the case the EPC will point at the
branch and the BD bit in the cause register (bit 31) will be set to
indicate this special case.
Ralf
next prev parent reply other threads:[~2007-11-20 18:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 23:52 futex_wake_op deadlock? Kaz Kylheku
2007-11-16 23:52 ` Kaz Kylheku
2007-11-19 18:48 ` Ralf Baechle
2007-11-19 21:27 ` Kaz Kylheku
2007-11-19 21:27 ` Kaz Kylheku
2007-11-19 21:42 ` Kaz Kylheku
2007-11-19 21:42 ` Kaz Kylheku
2007-11-20 11:21 ` Ralf Baechle
2007-11-20 18:06 ` Kaz Kylheku
2007-11-20 18:06 ` Kaz Kylheku
2007-11-20 18:16 ` Ralf Baechle [this message]
2007-11-20 18:24 ` Kaz Kylheku
2007-11-20 18:24 ` Kaz Kylheku
2007-11-20 18:29 ` David Daney
2007-11-20 19:00 ` Ralf Baechle
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=20071120181619.GA17979@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kaz@zeugmasystems.com \
--cc=linux-mips@linux-mips.org \
/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