From: Andi Kleen <ak@suse.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bugs aren't features: X86_FEATURE_FXSAVE_LEAK
Date: Fri, 5 May 2006 20:27:21 +0200 [thread overview]
Message-ID: <200605052027.21985.ak@suse.de> (raw)
In-Reply-To: <445B96E1.3080401@zytor.com>
On Friday 05 May 2006 20:18, H. Peter Anvin wrote:
> Andi Kleen wrote:
> > "H. Peter Anvin" <hpa@zytor.com> writes:
> >
> >> The recent fix for the AMD FXSAVE information leak had a problematic
> >> side effect. It introduced an entry in the x86 features vector which
> >> is a bug, not a feature.
> >
> > It's a non issue because it affects all AMD CPUs (except K5/K6).
> > You'll never find a system where only some CPUs have this problem.
> >
>
> It's still wrong architecturally, and we should have a sane way to deal with this as well
> as other bugs. This isn't the only bug -- we're getting a decent-size collection of them
> already -- and not all of them is going to have that particular property.
I'm not very worried because mixing steppings is generally unsupported anyways
and in Linux also doesn't work well with it.
(e.g. my old rig with one CPU FXSAVE capable, one CPU not never worked without
kernel hacks)
It's probably not worth the effort anyways. The people who build such strange
systems can tweak their kernels for it too.
-Andi
next prev parent reply other threads:[~2006-05-05 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 16:36 Bugs aren't features: X86_FEATURE_FXSAVE_LEAK H. Peter Anvin
2006-05-05 18:11 ` Andi Kleen
2006-05-05 18:18 ` H. Peter Anvin
2006-05-05 18:27 ` Andi Kleen [this message]
2006-05-06 4:16 ` Christer Weinigel
2006-05-09 14:38 ` Bill Davidsen
[not found] <69bvw-2zO-5@gated-at.bofh.it>
[not found] ` <69d4M-4Yx-19@gated-at.bofh.it>
[not found] ` <69mqY-1Ci-9@gated-at.bofh.it>
2006-05-06 17:37 ` Robert Hancock
2006-05-08 17:47 ` H. Peter Anvin
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=200605052027.21985.ak@suse.de \
--to=ak@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@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