From: Ralf Baechle <ralf@linux-mips.org>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>, a.voropay@equant.ru
Subject: Re: [PATCH] Fix process crash in 2.4 on attempt to use FPU on MIPS32
Date: Thu, 6 Jul 2006 23:57:18 +0100 [thread overview]
Message-ID: <20060706225718.GA18284@linux-mips.org> (raw)
In-Reply-To: <44AD7FBA.8000203@ru.mvista.com>
On Fri, Jul 07, 2006 at 01:25:14AM +0400, Sergei Shtylyov wrote:
> If there's built-in FPU in a MIPS32 CPU the first time the process tries
> to use it, the kernel should crash with "reserved instruction" -- CPU will
> try
> to execute 'dmtc1' which is a MIPS64 only insn. _init_fpu() was apprently
> blindly copied form arch/mips64/... :-)
>
> Since this occured with GXemul recently resending this 1.5 year old patch.
I didn't like the patch back then because it drops the optimizations
for 64-bit processors. So I just took the 2.6 variant of the code and
bolted it into 2.4.
Ralf
prev parent reply other threads:[~2006-07-06 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 21:25 [PATCH] Fix process crash in 2.4 on attempt to use FPU on MIPS32 Sergei Shtylyov
2006-07-06 22:57 ` Ralf Baechle [this message]
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=20060706225718.GA18284@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=a.voropay@equant.ru \
--cc=linux-mips@linux-mips.org \
--cc=sshtylyov@ru.mvista.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