From: "Kevin D. Kissell" <kevink@mips.com>
To: "Ralf Baechle" <ralf@oss.sgi.com>, "Jun Sun" <jsun@mvista.com>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: "Setting flush to zero for ..." - what is the warning?
Date: Fri, 3 Nov 2000 11:58:56 +0100 [thread overview]
Message-ID: <007d01c04585$25262e40$0deca8c0@Ulysses> (raw)
In-Reply-To: 20001102040657.A17786@bacchus.dhis.org
> On Wed, Nov 01, 2000 at 10:58:13AM -0800, Jun Sun wrote:
>
> > I ran some stress tests and start to get this warning. It appears to be
> > generated in do_fpe() routine. See below. I wonder why this is
> > happening. Can someone explain what is going on? Thanks.
>
> It tells you the over-the-thumb-fp-mode has been activated ;-)
More seriously, there was (is, in 2.4 I guess) a hack by which,
in a desperate attempt to avoid having to do the FP emulation
in software, the kernel changed the FPU denorm handling mode
and replayed the instruction, in hopes that the problem would
go away (which it would for a subset of the unimplemented
operation cases). This is not legal IEEE behaviour, as it turns out,
but not many people cared.
> Somebody at MIPS is working on merging the necessary fp support software
> into the kernel, so this problem should be solved soon.
Once we had bolted the Algorithmics FPU emulator into the kernel,
the hack was no longer necessary. To say that "somebody at MIPS
is working on merging the necessary fp support software into the
kernel" is perhaps a bit misleading. The FPU emulator itself is in
the oss.sgi.com repository, in the 2_2 branch, but I did not merge
in the hacks to the kernel exception, context, signal, etc. handling.
And there are several bug fixes that have been made since then.
All the additional code is available on the ftp.mips.com server, and
has been merged by others into 2.3/2.4, most notably by the VrLinux
guys.
We've got 2.4-test running in the lab, but it is a long way
from being as robust under torture as our 2.2 kernel, and
we have not decided whether it is "ripe" enough to merge
in the FPU emulation support ourselves.
Regards,
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Ralf Baechle <ralf@oss.sgi.com>, Jun Sun <jsun@mvista.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: "Setting flush to zero for ..." - what is the warning?
Date: Fri, 3 Nov 2000 11:58:56 +0100 [thread overview]
Message-ID: <007d01c04585$25262e40$0deca8c0@Ulysses> (raw)
Message-ID: <20001103105856.d0RazeD1HPoAfDNL4EBhrqBhBaHiP7HQzI6q706CqVw@z> (raw)
In-Reply-To: 20001102040657.A17786@bacchus.dhis.org
> On Wed, Nov 01, 2000 at 10:58:13AM -0800, Jun Sun wrote:
>
> > I ran some stress tests and start to get this warning. It appears to be
> > generated in do_fpe() routine. See below. I wonder why this is
> > happening. Can someone explain what is going on? Thanks.
>
> It tells you the over-the-thumb-fp-mode has been activated ;-)
More seriously, there was (is, in 2.4 I guess) a hack by which,
in a desperate attempt to avoid having to do the FP emulation
in software, the kernel changed the FPU denorm handling mode
and replayed the instruction, in hopes that the problem would
go away (which it would for a subset of the unimplemented
operation cases). This is not legal IEEE behaviour, as it turns out,
but not many people cared.
> Somebody at MIPS is working on merging the necessary fp support software
> into the kernel, so this problem should be solved soon.
Once we had bolted the Algorithmics FPU emulator into the kernel,
the hack was no longer necessary. To say that "somebody at MIPS
is working on merging the necessary fp support software into the
kernel" is perhaps a bit misleading. The FPU emulator itself is in
the oss.sgi.com repository, in the 2_2 branch, but I did not merge
in the hacks to the kernel exception, context, signal, etc. handling.
And there are several bug fixes that have been made since then.
All the additional code is available on the ftp.mips.com server, and
has been merged by others into 2.3/2.4, most notably by the VrLinux
guys.
We've got 2.4-test running in the lab, but it is a long way
from being as robust under torture as our 2.2 kernel, and
we have not decided whether it is "ripe" enough to merge
in the FPU emulation support ourselves.
Regards,
Kevin K.
next prev parent reply other threads:[~2000-11-03 10:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-01 18:58 "Setting flush to zero for ..." - what is the warning? Jun Sun
2000-11-02 3:06 ` Ralf Baechle
2000-11-03 10:58 ` Kevin D. Kissell [this message]
2000-11-03 10:58 ` Kevin D. Kissell
2000-11-03 17:55 ` Jun Sun
2000-11-03 18:55 ` Kevin D. Kissell
2000-11-03 18:55 ` Kevin D. Kissell
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='007d01c04585$25262e40$0deca8c0@Ulysses' \
--to=kevink@mips.com \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox