Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@mips.com>
To: "Dominic Sweetman" <dom@algor.co.uk>
Cc: "Linux SGI" <linux@cthulhu.engr.sgi.com>, <linux-mips@fnet.fr>,
	<linux-mips@vger.rutgers.edu>
Subject: Re: FP emulation patch available
Date: Tue, 21 Mar 2000 23:27:19 +0100	[thread overview]
Message-ID: <00f101bf9384$a2ec6230$0ceca8c0@satanas.mips.com> (raw)

>> Denormalised operands (for example) will cause any computational
>> operation to blow up (change sign, load, store and move will survive -
>> can you think of much else?).  The requirement for MIPS hardware is
>> something like "you can throw an unimplemented exception in response
>> to any combination of operands and operation you don't like, so long
>> as it's rare".  That's why a complete emulator is probably a good
>> idea.
>>
>> Dominic Sweetman
>> dom@algor.co.uk
>
>OK, I'm convinced.  I believe I know how to make the Algorithmics
>emulator SMP-safe *and* more efficient in the general case, thanks
>in part to a suggestion from Ralf.  Time permitting, I will also wire it
>up to the unimplemented operation handler.  Give me a week or so
>to accumulate enough spare time...


OK, I've done it, and it seems to work very nicely indeed.
The combination of a real FPU with the Algorithmics emulator
for the Unimplemented corner case has given me the first
100% successful "paranoia" runs I've seen under MIPS Linux.
I also merged in some R3000 fixes that Harald pointed out
to me.  I'm holding off on distribution to give my colleagues
some time to merge in some CP0 hazard fixes, but we'll be 
putting the sources and patches up on the web in the next 
few days...

            Kevin K.

WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Dominic Sweetman <dom@algor.co.uk>
Cc: Linux SGI <linux@cthulhu.engr.sgi.com>,
	linux-mips@fnet.fr, linux-mips@vger.rutgers.edu
Subject: Re: FP emulation patch available
Date: Tue, 21 Mar 2000 23:27:19 +0100	[thread overview]
Message-ID: <00f101bf9384$a2ec6230$0ceca8c0@satanas.mips.com> (raw)
Message-ID: <20000321222719.M5VydjQVtLxkN95X4P2sG0HbxuB3HZYuiA32FLPTb5U@z> (raw)

>> Denormalised operands (for example) will cause any computational
>> operation to blow up (change sign, load, store and move will survive -
>> can you think of much else?).  The requirement for MIPS hardware is
>> something like "you can throw an unimplemented exception in response
>> to any combination of operands and operation you don't like, so long
>> as it's rare".  That's why a complete emulator is probably a good
>> idea.
>>
>> Dominic Sweetman
>> dom@algor.co.uk
>
>OK, I'm convinced.  I believe I know how to make the Algorithmics
>emulator SMP-safe *and* more efficient in the general case, thanks
>in part to a suggestion from Ralf.  Time permitting, I will also wire it
>up to the unimplemented operation handler.  Give me a week or so
>to accumulate enough spare time...


OK, I've done it, and it seems to work very nicely indeed.
The combination of a real FPU with the Algorithmics emulator
for the Unimplemented corner case has given me the first
100% successful "paranoia" runs I've seen under MIPS Linux.
I also merged in some R3000 fixes that Harald pointed out
to me.  I'm holding off on distribution to give my colleagues
some time to merge in some CP0 hazard fixes, but we'll be 
putting the sources and patches up on the web in the next 
few days...

            Kevin K.

             reply	other threads:[~2000-03-21 22:43 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-21 22:27 Kevin D. Kissell [this message]
2000-03-21 22:27 ` FP emulation patch available Kevin D. Kissell
  -- strict thread matches above, loose matches on Subject: below --
2000-03-13 23:20 Kevin D. Kissell
2000-03-13 23:20 ` Kevin D. Kissell
2000-03-14 18:15 ` Harald Koerfgen
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='00f101bf9384$a2ec6230$0ceca8c0@satanas.mips.com' \
    --to=kevink@mips.com \
    --cc=dom@algor.co.uk \
    --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