linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@freescale.com>
To: "Tom Rini" <trini@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] invalid instructions in kernel mode
Date: Thu, 7 Apr 2005 16:41:59 -0500	[thread overview]
Message-ID: <f3f5e13e4c8b3cb7b327fb51db84150d@freescale.com> (raw)
In-Reply-To: <20050407173821.GQ3396@smtp.west.cox.net>


On Apr 7, 2005, at 12:38 PM, Tom Rini wrote:

> On Thu, Mar 31, 2005 at 07:47:32PM +0200, Fillod Stephane wrote:
>
> > When CPU has no (classic) FPU, and math emulation is disabled,
>  > fp instructions are not allowed in kernel mode.
>  [snip]
>  > --- linux/arch/ppc/kernel/misc.S=A0=A0=A0=A0=A0 26 Mar 2005 =
03:28:36 -0000
>  > 1.1.1.2
>  > +++ linux/arch/ppc/kernel/misc.S=A0=A0=A0=A0=A0 31 Mar 2005 =
16:33:25 -0000
>  > @@ -1096,7 +1096,8 @@
>  >=A0=A0 * and exceptions as if the cpu had performed the load or =
store.
>  >=A0=A0 */
>  >=A0
> > -#if defined(CONFIG_4xx) || defined(CONFIG_E500)
> > +#if !(defined(CONFIG_4xx) || defined(CONFIG_E500) ||
>  > defined(CONFIG_8xx)) ||=A0 defined(CONFIG_MATH_EMULATION)
> > +#if defined(CONFIG_4xx) || defined(CONFIG_E500)
> >=A0 _GLOBAL(cvt_fd)
> >=A0 =A0=A0=A0=A0 lfs=A0=A0=A0=A0 0,0(r3)
>  >=A0 =A0=A0=A0=A0 stfd=A0=A0=A0 0,0(r4)
>  > @@ -1125,6 +1126,7 @@
>  >=A0 =A0=A0=A0=A0 stfd=A0=A0=A0 0,-4(r5)
>  >=A0 =A0=A0=A0=A0 blr
>  >=A0 #endif
>  > +#endif
>
> The problem here is, HEY! (classic) FP instrs in the kernel.=A0 The
>  question is why?=A0 Or rather, why are these four classic FP instrs
>  (lfs/lfd/stfd/stfs) being done on CONFIG_4xx || E500 when neither has
>  classic FP?=A0 I think the problem here is that on !FPU
> (which is 4xx||E500||8xx, or so), we need to rewrite these two
>  functions (yes, 8xx does emulate them if hit, but that's a tangent).

What is not clear to me is what condition causes these to get hit on an=20=

e500.

- kumar

  reply	other threads:[~2005-04-07 21:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31 17:47 [PATCH] invalid instructions in kernel mode Fillod Stephane
2005-03-31 18:15 ` Dan Malek
2005-04-01 10:04 ` Kumar Gala
2005-04-07 17:38 ` Tom Rini
2005-04-07 21:41   ` Kumar Gala [this message]
2005-04-07 22:14     ` Tom Rini
2005-04-07 22:29       ` Kumar Gala
2005-04-08 16:02         ` Kumar Gala
  -- strict thread matches above, loose matches on Subject: below --
2005-03-31 19:17 Fillod Stephane
2005-04-01  3:45 ` Dan Malek
2005-04-05 12:24 Fillod Stephane
2005-04-05 16:16 ` Dan Malek
2005-04-05 12:25 Fillod Stephane
2005-04-08 17:36 Fillod Stephane
2005-04-11 15:39 ` Kumar Gala

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=f3f5e13e4c8b3cb7b327fb51db84150d@freescale.com \
    --to=kumar.gala@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).