From: Andi Kleen <ak@suse.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, jbeulich@novell.com
Subject: Re: [PATCH] fxsave/fxrstor adjustments
Date: 25 Apr 2006 02:56:17 +0200 [thread overview]
Message-ID: <p737j5ea2xa.fsf@bragg.suse.de> (raw)
In-Reply-To: <ba522d64e7bde4de804093e54f8dd568@cl.cam.ac.uk>
Keir Fraser <Keir.Fraser@cl.cam.ac.uk> writes:
> On 24 Apr 2006, at 16:31, Jan Beulich wrote:
>
> > This patch addresses CVE-2006-1056 (information leak from
> > fxsave/fxrstor on AMD CPUs) and also adjusts 64-bit handling
> > so that full 64-bit RIP/RDP values get saved/restored. More
> > fine-grained handling may be needed if 32-bit processes are
> > expected to properly see their selectors (native Linux doesn't
> > currently do that either, but there is a patch to adjust
> > it there).
>
> Why does this patch (and the one in Linux 2.6.16.9) use 'emms' in the
> fxsave path rather than 'ffree st(7)' which is what AMD recommends in
> their published advisory? Is the former faster?
On K7/K8 emms and ffree st(7) are the same performance. On P4 ffree is
much faster. The Linux 2.6 patch uses emms because it patches the code
in only on K7/K8. For the Xen patch that's ok too although it checks,
not patches. In Linux 2.4 where the code is executed unconditionally
ffree is used.
An earlier version of the AMD workaround used emms always until
the P4 emms performance issue was discovered.
-Andi
next prev parent reply other threads:[~2006-04-25 0:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 15:31 [PATCH] fxsave/fxrstor adjustments Jan Beulich
2006-04-24 16:14 ` Keir Fraser
2006-04-25 0:56 ` Andi Kleen [this message]
2006-04-25 7:51 ` Keir Fraser
2006-04-25 6:54 ` Jan Beulich
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=p737j5ea2xa.fsf@bragg.suse.de \
--to=ak@suse.de \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.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 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.