From: "Kevin D. Kissell" <kevink@mips.com>
To: "Harald Koerfgen" <Harald.Koerfgen@home.ivm.de>
Cc: "Linux SGI" <linux@cthulhu.engr.sgi.com>,
"Linux/MIPS fnet" <linux-mips@fnet.fr>,
<linux-mips@vger.rutgers.edu>
Subject: Re: FP emulation patch available
Date: Tue, 14 Mar 2000 00:20:36 +0100 [thread overview]
Message-ID: <005a01bf8d42$c656d2c0$ec44e8c3@Ulysses> (raw)
Herald Koerfgen writes:
>Personally, I don't have any idea why the emulator works perfectly on an
R3000
>but not on an R3912.
Nor I, but in the absence of data, I'm happy to speculate. ;-)
...
>Oh I see, I should have made myself more clear. I have a root filesystem on
a
>CF card based on declinuxroot (a cut down RedHat 5.1) and my Mobilon boots
all
>the way through to the login prompt if I delete the fsck from the
initscripts.
>
>Booting into single user mode I can easily verify that tools like df or
e2fsck
>are bombing out with floating point exeptions. My "tests" with the emulator
>have been so far: Does df survive? What does fsck do? and things like that.
>Well, with the emulator all these tools make the Mobilon crash. Hard. So
hard
>that even the reset button doesn't work.
There are two ways in which the FPU emulator is close enough
to the hardware to be this sensitive to implementation. One
is the way the emulator provokes an address error exception to
execute a delay slot instruction following a simulated branch, but
I don't think df or fsck do any branch-on-floating-conditions. The
other is, of course, that it counts on getting sensible and recoverable
coprocessor unusable exceptions. If the R3912 does something
funky to the processor state on a CP1 unusable fault - an event
that it doesn't have to deal with in its principal mission
as a Windows CE platform - the results would be much
what you are seeing.
There are people at Toshiba who read this mailing
list, so we can hope that they too are on the case and
can maybe lend a clue...
Regards,
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Harald Koerfgen <Harald.Koerfgen@home.ivm.de>
Cc: Linux SGI <linux@cthulhu.engr.sgi.com>,
Linux/MIPS fnet <linux-mips@fnet.fr>,
linux-mips@vger.rutgers.edu
Subject: Re: FP emulation patch available
Date: Tue, 14 Mar 2000 00:20:36 +0100 [thread overview]
Message-ID: <005a01bf8d42$c656d2c0$ec44e8c3@Ulysses> (raw)
Message-ID: <20000313232036.ROw_AvC9RRvixujTkcOe89-m91dzFN8JNva4dsRCGvU@z> (raw)
Herald Koerfgen writes:
>Personally, I don't have any idea why the emulator works perfectly on an
R3000
>but not on an R3912.
Nor I, but in the absence of data, I'm happy to speculate. ;-)
...
>Oh I see, I should have made myself more clear. I have a root filesystem on
a
>CF card based on declinuxroot (a cut down RedHat 5.1) and my Mobilon boots
all
>the way through to the login prompt if I delete the fsck from the
initscripts.
>
>Booting into single user mode I can easily verify that tools like df or
e2fsck
>are bombing out with floating point exeptions. My "tests" with the emulator
>have been so far: Does df survive? What does fsck do? and things like that.
>Well, with the emulator all these tools make the Mobilon crash. Hard. So
hard
>that even the reset button doesn't work.
There are two ways in which the FPU emulator is close enough
to the hardware to be this sensitive to implementation. One
is the way the emulator provokes an address error exception to
execute a delay slot instruction following a simulated branch, but
I don't think df or fsck do any branch-on-floating-conditions. The
other is, of course, that it counts on getting sensible and recoverable
coprocessor unusable exceptions. If the R3912 does something
funky to the processor state on a CP1 unusable fault - an event
that it doesn't have to deal with in its principal mission
as a Windows CE platform - the results would be much
what you are seeing.
There are people at Toshiba who read this mailing
list, so we can hope that they too are on the case and
can maybe lend a clue...
Regards,
Kevin K.
next reply other threads:[~2000-03-13 23:36 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-13 23:20 Kevin D. Kissell [this message]
2000-03-13 23:20 ` FP emulation patch available Kevin D. Kissell
2000-03-14 18:15 ` Harald Koerfgen
-- strict thread matches above, loose matches on Subject: below --
2000-03-21 22:27 Kevin D. Kissell
2000-03-21 22:27 ` Kevin D. Kissell
2000-03-13 8:33 Kevin D. Kissell
2000-03-13 8:33 ` Kevin D. Kissell
2000-03-13 13:46 ` Alan Cox
2000-03-13 13:46 ` Alan Cox
2000-03-13 19:05 ` Harald Koerfgen
2000-03-13 19:05 ` Harald Koerfgen
2000-03-13 17:46 ` Ralf Baechle
2000-03-13 20:13 ` William J. Earl
2000-03-14 18:50 ` Andrew R. Baker
[not found] ` <200003142317.XAA00644@gladsmuir.algor.co.uk>
2000-03-15 14:35 ` Kevin D. Kissell
2000-03-12 21:52 Kevin D. Kissell
2000-03-12 21:52 ` Kevin D. Kissell
2000-03-13 22:22 ` Harald Koerfgen
2000-03-12 13:03 Kevin D. Kissell
2000-03-12 13:03 ` Kevin D. Kissell
2000-03-12 21:23 ` Harald Koerfgen
2000-03-08 20:12 Kevin D. Kissell
2000-03-08 20:12 ` Kevin D. Kissell
2000-03-09 2:03 ` Warner Losh
[not found] ` <200003082223.WAA00605@gladsmuir.algor.co.uk>
2000-03-09 2:13 ` Warner Losh
2000-03-09 20:20 ` Harald Koerfgen
2000-03-08 9:43 Kevin D. Kissell
2000-03-08 9:43 ` Kevin D. Kissell
2000-03-08 17:02 ` Richard van den Berg
2000-03-08 18:43 ` Harald Koerfgen
2000-03-07 4:12 Andrew R. Baker
[not found] ` <097a01bf87eb$ebe4d4d0$b8119526@ltc.com>
[not found] ` <38C4C328.9656C68E@niisi.msk.ru>
2000-03-07 18:54 ` Andrew R. Baker
2000-03-07 19:43 ` Harald Koerfgen
2000-03-08 16:11 ` Ralf Baechle
[not found] ` <200003071022.KAA00275@gladsmuir.algor.co.uk>
2000-03-07 12:08 ` Jay Carlson
2000-03-07 12:08 ` Jay Carlson
2000-03-08 16:25 ` Ralf Baechle
2000-03-08 16:18 ` 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='005a01bf8d42$c656d2c0$ec44e8c3@Ulysses' \
--to=kevink@mips.com \
--cc=Harald.Koerfgen@home.ivm.de \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@vger.rutgers.edu \
--cc=linux@cthulhu.engr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox