All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Jim Hull <jim.hull@hp.com>
Cc: 'John David Anglin' <dave@hiauly1.hia.nrc.ca>,
	parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Re: floating point exception error
Date: Fri, 10 Jan 2003 22:16:38 -0800	[thread overview]
Message-ID: <20030111061638.GH31470@tausq.org> (raw)
In-Reply-To: <005c01c2b8f7$e79cc8c0$6763f40f@cup.hp.com>

> Ok, that's good to hear.  Your info, along with Randolph's info that it
> traps on the 8500, 8600, and 8700 CPUs, leads me to the same conclusion
> as Randolph came to.  It looks like there's something wrong with the
> fcnv emulation in the linux kernel's emulation handler, even though it
> was derived from the hpux handler, where everything appears to work
> fine.

I think i found it....

for class 1 ops (fcnv) pa20 has a 3-bit subop field, pa11 has a 2-bit
subop field, which determines the source/target formats. our code is not
correctly determining pa11 vs pa20, so it defaults to pa11 and uses
subop==1 instead of subop==5

now, the tricky part is how to get it to detect the right type. the code
looks like this:

fpu_type_flags=fpregs[FPU_TYPE_FLAG_POS];  /* get fpu type flags */
if  (fpu_type_flags & PA2_0_FPU_FLAG)
    subop = get_subop1_PA2_0(ir);
else
    subop = get_subop1_PA1_1(ir);

FPU_TYPE_FLAG_POS is defined as
#define EM_FPU_TYPE_OFFSET 272
#define FPU_TYPE_FLAG_POS (EM_FPU_TYPE_OFFSET>>2)
(272>>2 == 68)

so, i wonder:
1) why those numbers? (where is it documented?)
2) is there a special way to read that fpu type from the fpu? or do we
use boot_cpu_data.cpu_type?

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

  reply	other threads:[~2003-01-11  6:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11 21:13 [parisc-linux] ["CSA Test Drive" <TestDrive@compaq.com>] FW: Some issues Bdale Garbee
2002-12-11 22:03 ` John David Anglin
2002-12-11 22:44   ` Carlos O'Donell
2002-12-11 23:05     ` John David Anglin
2002-12-11 23:17       ` Carlos O'Donell
2002-12-12  6:50       ` Randolph Chung
2002-12-12 12:15         ` Matthew Wilcox
2003-01-10  7:54       ` [parisc-linux] Re: floating point exception error Randolph Chung
2003-01-10 18:08         ` Jim Hull
2003-01-10 18:35           ` Randolph Chung
2003-01-10 18:48           ` John David Anglin
2003-01-10 22:30             ` Jim Hull
2003-01-11  6:16               ` Randolph Chung [this message]
2003-01-11  7:10                 ` Grant Grundler
2003-01-11 18:31                 ` John David Anglin
2003-01-12  8:37                   ` Randolph Chung
2003-01-13 15:58                     ` jsoe0708
2003-01-13 16:57                       ` Randolph Chung
2003-01-13 17:16                         ` jsoe0708
2003-01-13 17:16                           ` Randolph Chung

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=20030111061638.GH31470@tausq.org \
    --to=randolph@tausq.org \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=jim.hull@hp.com \
    --cc=parisc-linux@parisc-linux.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 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.