From: Jun Sun <jsun@mvista.com>
To: linux-mips@oss.sgi.com
Subject: FPU emulator unsafe for SMP?
Date: Thu, 14 Feb 2002 17:56:31 -0800 [thread overview]
Message-ID: <3C6C6ACF.CAD2FFC@mvista.com> (raw)
I have been chasing a FPU register corruption problem on a SMP box. The
curruption seems to be caused by FPU emulator code. Is that code SMP safe?
If not, what are the volunerable spots?
Just thought I'd check before I dive into it ....
BTW, I think even with the latest fpu emu patch, the classic fpu/signal
problem is still there. I will post in a separate email later.
Jun
next reply other threads:[~2002-02-15 2:56 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-15 1:56 Jun Sun [this message]
2002-02-15 2:11 ` FPU emulator unsafe for SMP? Ralf Baechle
2002-02-15 7:20 ` Jun Sun
2002-02-15 8:30 ` Jun Sun
2002-02-15 9:59 ` Kevin D. Kissell
2002-02-15 9:59 ` Kevin D. Kissell
2002-02-19 22:05 ` Jun Sun
2002-02-19 22:19 ` Ralf Baechle
2002-02-20 0:08 ` Kevin D. Kissell
2002-02-20 0:08 ` Kevin D. Kissell
2002-02-20 1:12 ` Jun Sun
2002-02-20 3:28 ` Greg Lindahl
2002-02-20 4:24 ` Jun Sun
2002-02-20 4:32 ` Daniel Jacobowitz
2002-02-20 9:48 ` Jun Sun
2002-02-20 10:14 ` Kevin D. Kissell
2002-02-20 10:14 ` Kevin D. Kissell
2002-02-20 13:50 ` Ralf Baechle
2002-02-20 20:53 ` Greg Lindahl
2002-02-20 13:24 ` Ralf Baechle
2002-02-20 4:48 ` Greg Lindahl
2002-02-20 9:27 ` Florian Lohoff
2002-02-20 13:18 ` Ralf Baechle
2002-02-20 9:56 ` Geert Uytterhoeven
2002-02-20 11:14 ` Kevin D. Kissell
2002-02-20 13:10 ` Ralf Baechle
2002-02-20 8:27 ` Dominic Sweetman
2002-02-20 9:30 ` Florian Lohoff
2002-02-20 13:56 ` Ralf Baechle
2002-02-20 13:09 ` Ralf Baechle
2002-02-20 14:42 ` Kevin D. Kissell
2002-02-20 14:42 ` Kevin D. Kissell
2002-02-20 14:46 ` Maciej W. Rozycki
2002-02-20 15:05 ` Ralf Baechle
2002-02-20 15:45 ` Maciej W. Rozycki
2002-02-20 13:03 ` Ralf Baechle
2002-02-15 8:14 ` Kevin D. Kissell
2002-02-15 8:14 ` Kevin D. Kissell
2002-02-15 10:57 ` Ralf Baechle
2002-02-19 22:02 ` Jun Sun
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=3C6C6ACF.CAD2FFC@mvista.com \
--to=jsun@mvista.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.