From: Chris Mason <mason@suse.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] High fpu register corruption
Date: Thu, 08 May 2003 16:42:27 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705683@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705679@msgid-missing>
On Thu, 2003-05-08 at 12:33, Mallick, Asit K wrote:
> Andreas,
>
> The high FP save and restore in the context switch makes the
> assumption that user will not be modifying the psr.mfh and it will be
> only updated by the hardware. Without this assumption we can not
> optimize the FP save/restore for SMP systems (this patch will not
> cover all cases). If application wants the current high fpu state to
> be preserved then it should will not be able to modify the psr.mfh.
>
> What kind of applications are trying to modify the mfh?
The ia64 ssl source has hand optimized asm that clears mfh, but that
doesn't really matter. What matters is that any application can do it,
so it has security implications.
-chris
next prev parent reply other threads:[~2003-05-08 16:42 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 [this message]
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
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-105590723705683@msgid-missing \
--to=mason@suse.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