public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn_helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] High fpu register corruption (PATCH)
Date: Thu, 29 May 2003 03:53:13 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723706065@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705679@msgid-missing>

On Thursday 22 May 2003 3:55 pm, Mallick, Asit K wrote:
> Attached is a patch to fix the high FPU corruption (thanks to Andreas
> and Chris). This patch also unifies the FPU save/restore for SMP and UP
> and also fixes another problem with FPH save/restore path due to an
> unaligned fault.

I'm comparing 2.4 (including your patch) and David's current
2.5 BK tree.  I'd like to keep them as close as possible, but
I see several clearly gratuitous differences (like whitespace)
and some that aren't obvious to me.

arch/ia64/kernel/ptrace.c:
	2.4 calls ia64_drop_fpu() from ia64_sync_fph().
	2.5 calls ia64_drop_fpu() from ia64_flush_fph().
	Is there a reason for the difference?

arch/ia64/kernel/setup.c:
	cpu_init(): 2.4 added ia64_set_kr() and removed
	ia64_set_fpu_owner(); 2.5 doesn't have this change.
	This looks like at least partly a bug in 2.5 --
	ia64_set_fpu_owner is called under "#ifndef CONFIG_SMP"
	but not defined anywhere.

arch/ia64/kernel/signal.c:
	restore_sigcontext() changes look equivalent, but have
	gratuitous differences from 2.5 (reversed sense of test,
	comment)

arch/ia64/kernel/traps.c:
	disabled_fph_fault(): 2.4 uses ia64_is_local_fpu_owner();
	2.5 uses "fpu_owner = current".  Is there a reason for
	this?

	Also gratuitous whitespace differences.

include/asm-ia64/processor.h:
	ia64_is_local_fpu_owner(), ia64_set_local_fpu_owner():
	these look functionally equivalent in 2.4 and 2.5.
	Can they be made identical?

include/asm-ia64/system.h:
	IA64_HAS_EXTRA_STATE() and switch_to() appear to be
	identical in 2.4 and 2.5 except for whitespace changes.
	Can they be made identical?

Any insight would be appreciated!

Bjorn



  parent reply	other threads:[~2003-05-29  3:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 14:16 [Linux-ia64] High fpu register corruption Andreas Schwab
2003-05-08 16:33 ` Mallick, Asit K
2003-05-08 16:42 ` Chris Mason
2003-05-08 16:58 ` David Mosberger
2003-05-08 17:03 ` David Mosberger
2003-05-08 17:14 ` Mallick, Asit K
2003-05-08 17:55 ` David Mosberger
2003-05-22 21:55 ` [Linux-ia64] High fpu register corruption (PATCH) Mallick, Asit K
2003-05-29  3:53 ` Bjorn Helgaas [this message]
2003-05-29  4:10 ` David Mosberger
2003-05-29  4:25 ` Bjorn Helgaas
2003-05-29  4:40 ` David Mosberger
2003-05-29  5:43 ` Mallick, Asit K

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=marc-linux-ia64-105590723706065@msgid-missing \
    --to=bjorn_helgaas@hp.com \
    --cc=linux-ia64@vger.kernel.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