From: Kumar Gala <kumar.gala@freescale.com>
To: Dan Malek <dan@embeddededge.com>,
Fillod Stephane <stephane.fillod@thomson.net>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] invalid instructions in kernel mode
Date: Mon, 11 Apr 2005 10:39:20 -0500 [thread overview]
Message-ID: <ccf472df421e6d08840588571af40aaa@freescale.com> (raw)
In-Reply-To: <1CFEB358338412458B21FAA0D78FE86D4F0D39@rennsmail02.eu.thmulti.com>
Ok,
After some debug on Friday and this weekend I understand what's going=20
on. The reason we hit the code path in the kernel is due to the fact=20
that we are actually executing an integer load/store that is=20
misaligned, however when we read the instruction from memory we get a=20
float point instruction. This is due to the fact that test app is not=20=
properly handling its self generated code.
Note, I was testing with math-emu turned on.
It seems to me that when we introduce CONFIG_PPC_FPU that we ifdef=20
around the code and return 0 in the 44x/e500 cases w/o FPUs
- kumar
On Apr 8, 2005, at 12:36 PM, Fillod Stephane wrote:
> Kumar Gala wrote:
> > Are you running this via a ramdisk or nfs?=A0 If ramdisk can you =
post=20
> it
>
> > somewhere that I can get to?
>
> I'm running via NFS.
>
> > Also, can you email the list with the kernel oops that shows up.
>
> I'll do that next week.
>
> Anyway, reading the source suffices to realize there's a problem when
> MATH_EMULATION is disabled on a FPU-less system with user programs
> using load/store fp instructions.
>
> --=20
> Stephane
next prev parent reply other threads:[~2005-04-11 15:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 17:36 [PATCH] invalid instructions in kernel mode Fillod Stephane
2005-04-11 15:39 ` Kumar Gala [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-05 12:25 Fillod Stephane
2005-04-05 12:24 Fillod Stephane
2005-04-05 16:16 ` Dan Malek
2005-03-31 19:17 Fillod Stephane
2005-04-01 3:45 ` Dan Malek
2005-03-31 17:47 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
2005-04-07 22:14 ` Tom Rini
2005-04-07 22:29 ` Kumar Gala
2005-04-08 16:02 ` 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=ccf472df421e6d08840588571af40aaa@freescale.com \
--to=kumar.gala@freescale.com \
--cc=dan@embeddededge.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=stephane.fillod@thomson.net \
/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).