From: Carsten Langgaard <carstenl@mips.com>
To: linux-mips@oss.sgi.com
Subject: Bug in the _save_fp_context.
Date: Mon, 19 Mar 2001 15:07:15 +0100 [thread overview]
Message-ID: <3AB61293.5652407C@mips.com> (raw)
I think there is a bug in the _save_fp_context function in
arch/mips/kernel/r4k_fpu.S
The problem is the following piece of code:
jr ra
.set nomacro
EX(sw t0,SC_FPC_EIR(a0))
nop
.set macro
First of all what should the ".set nomacro" do?
If it means that the EX macro shouldn't be used then this entry wouldn't
get into __ex_table, which would be wrong.
But it look like it uses the macro anyway, regardless of the ".set
nomacro", at least with the compiler I use.
Never the less we do not handle entries in the __ex_table which is
located in a branch delay.
So we need to handle the situation where we take a page fault on an
instruction which is located in a brach delay slot, or we don't put the
"potential" faulting instruction in a delay slot.
Any ideas, how we should handle this in a nice and clean way?
/Carsten
--
_ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com
|\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
| \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556
Denmark http://www.mips.com
next reply other threads:[~2001-03-19 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-19 14:07 Carsten Langgaard [this message]
2001-03-19 15:43 ` Bug in the _save_fp_context Kevin D. Kissell
2001-03-19 15:43 ` Kevin D. Kissell
2001-03-19 16:03 ` Kevin D. Kissell
2001-03-19 16:03 ` Kevin D. Kissell
2001-03-19 18:14 ` Jun Sun
2001-03-19 16:13 ` Carsten Langgaard
2001-03-19 18:10 ` SCSI card [Re: Bug in the _save_fp_context.] Jun Sun
-- strict thread matches above, loose matches on Subject: below --
2002-01-17 13:34 Bug in the _save_fp_context Carsten Langgaard
[not found] ` <20020610114323.A25705@lucon.org>
2002-06-10 19:41 ` Carsten Langgaard
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=3AB61293.5652407C@mips.com \
--to=carstenl@mips.com \
--cc=linux-mips@oss.sgi.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.