From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] ar.fpsr not set on MCA/INIT kernel entry
Date: Mon, 18 Sep 2006 22:30:01 +0000 [thread overview]
Message-ID: <25493.1158618601@ocs3.ocs.com.au> (raw)
In-Reply-To: <200609182118.k8ILISN85963198@clink.americas.sgi.com>
Russ Anderson (on Mon, 18 Sep 2006 16:18:28 -0500 (CDT)) wrote:
>[patch] ar.fpsr not set on MCA/INIT kernel entry
>Index: test/arch/ia64/kernel/mca_asm.S
>=================================>--- test.orig/arch/ia64/kernel/mca_asm.S 2006-09-18 16:10:06.058062990 -0500
>+++ test/arch/ia64/kernel/mca_asm.S 2006-09-18 16:10:29.628971888 -0500
>@@ -1063,7 +1063,9 @@ ia64_set_kernel_registers:
> ;;
> mov IA64_KR(CURRENT_STACK)=r16
> or r21=r20,r21 // construct PA | page properties
>+ movl r17=FPSR_DEFAULT
> ;;
>+ mov.m ar.fpsr=r17 // set ar.fpsr to kernel default value
> mov cr.itir=r18
> mov cr.ifa=r13
> mov r20=IA64_TR_CURRENT_STACK
Any particular reason to place those instructions in the middle of the
code that wires IA64_TR_CURRENT_STACK? I tried to keep the tr code as
standard as possible, to make it easier to change in future. This code
is not performance sensitive, readability counts more than a couple of
unused slots here.
next prev parent reply other threads:[~2006-09-18 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 21:18 [patch] ar.fpsr not set on MCA/INIT kernel entry Russ Anderson
2006-09-18 22:30 ` Keith Owens [this message]
2006-09-18 23:37 ` Russ Anderson
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=25493.1158618601@ocs3.ocs.com.au \
--to=kaos@sgi.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