From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: preempt safe fpu-emulator
Date: Thu, 28 Apr 2005 14:41:18 +0100 [thread overview]
Message-ID: <20050428134118.GC1276@linux-mips.org> (raw)
In-Reply-To: <20050427.143622.77402407.nemoto@toshiba-tops.co.jp>
On Wed, Apr 27, 2005 at 02:36:22PM +0900, Atsushi Nemoto wrote:
> Hi. Here is a patch to make the fpu-emulator preempt-safe. It would
> be SMP-safe also.
>
> The 'ieee754_csr' global variable is removed. Now the 'ieee754_csr'
> is an alias of current->thread.fpu.soft.fcr31. While the fpu-emulator
> uses different mapping for RM bits (FPU_CSR_Rm vs. IEEE754_Rm), RM
> bits are converted before (and after) calling of cop1Emulate(). If we
> adjusted IEEE754_Rm to match with FPU_CSR_Rm, we can remove ieee_rm[]
> and mips_rm[]. Should we do it?
>
> With this patch, whole fpu-emulator can be run without disabling
> preempt. I will post a patch to fix preemption issue soon.
I applied both your patches with some slight cleanup for the endianess
stuff in arch/mips/math-emu/ieee754.h and non-Linux stuff.
Ralf
next prev parent reply other threads:[~2005-04-28 13:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 5:36 preempt safe fpu-emulator Atsushi Nemoto
2005-04-27 5:46 ` Atsushi Nemoto
2005-04-27 10:49 ` New Forum for support of RB500 (MIPS board) John Tully
2005-04-28 13:41 ` Ralf Baechle [this message]
2005-04-28 13:58 ` preempt safe fpu-emulator Kevin D. Kissell
2005-04-28 13:58 ` Kevin D. Kissell
2005-04-28 15:21 ` Ralf Baechle
2005-04-28 15:25 ` Maciej W. Rozycki
2005-04-28 15:33 ` Ralf Baechle
2005-04-28 15:34 ` Ralf Baechle
2005-04-28 16:06 ` Kevin D. Kissell
2005-04-28 16:06 ` Kevin D. Kissell
2005-04-29 13:40 ` Atsushi Nemoto
2005-04-30 14:36 ` Atsushi Nemoto
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=20050428134118.GC1276@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
/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