From: Andi Kleen <ak@suse.de>
To: paubert <paubert@iram.es>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>, Andi Kleen <ak@suse.de>,
David Mosberger <davidm@hpl.hp.com>
Subject: Re: [PATCH] Mask mxcsr according to cpu features.
Date: Fri, 9 May 2003 04:24:17 +0200 [thread overview]
Message-ID: <20030509022417.GB15829@Wotan.suse.de> (raw)
In-Reply-To: <20030509004200.A22795@mrt-lx16.iram.es>
On Fri, May 09, 2003 at 12:42:01AM +0000, paubert wrote:
>
> [CC'ed to x86_64 and ia64 maintainers because they might have the
> same issues. For existing x86_64 processors, s/0xffbf/0xffff/ in
> arch/x86-64/ia32/{fpu32,ptrace32}.c might be sufficient]
>
> With SSE2, mxcsr bit 6 is defined as controlling whether
> denormals should be treated as zeroes or not. Setting it
> no more causes an exception, but with the current code it
> would be cleared at every signal return which is a bit harsh.
>
> The following patch fixes this (2.5, but easily ported to 2.4).
x86-64 does it in a different way. It just handles the
possible exception on FXRSTOR with an __ex_table handler.
With that all the mxcsr masking can be dropped.
It was already this way for 64bit programs, but the 32bit emulation
still masks. I'm not sure I can change that - in theory it could
break existing programs.
-Andi
next prev parent reply other threads:[~2003-05-09 2:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 0:42 paubert
2003-05-09 2:24 ` Andi Kleen [this message]
2003-05-09 10:56 ` paubert
2003-05-09 11:41 ` Andi Kleen
2003-05-09 6:32 ` Philippe Elie
2003-05-09 10:48 ` paubert
2003-05-09 16:33 ` Philippe Elie
2003-05-09 16:50 ` paubert
2003-05-09 21:00 ` Philippe Elie
2003-05-11 23:31 ` [PATCH] [CFT] [RFC] Correct mxcsr handling (was: Mask mxcsr according to cpu features.) Gabriel Paubert
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=20030509022417.GB15829@Wotan.suse.de \
--to=ak@suse.de \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paubert@iram.es \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®