From: Christer Weinigel <christer@weinigel.se>
To: Andi Kleen <ak@suse.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: Bugs aren't features: X86_FEATURE_FXSAVE_LEAK
Date: 06 May 2006 06:16:54 +0200 [thread overview]
Message-ID: <m3iroju6rt.fsf@zoo.weinigel.se> (raw)
In-Reply-To: <p733bfo5ol1.fsf@bragg.suse.de>
Andi Kleen <ak@suse.de> writes:
> "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.
I have a dual CPU system (Tyan Tomcat 1564D) where only one CPU is
reported to have the F00F bug (iirc). So yes, there can be
SMP-systems where the CPU's have different bugs.
/Christer
--
"Just how much can I get away with and still go to heaven?"
Freelance consultant specializing in device driver programming for Linux
Christer Weinigel <christer@weinigel.se> http://www.weinigel.se
next prev parent reply other threads:[~2006-05-06 4:16 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
2006-05-06 4:16 ` Christer Weinigel [this message]
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=m3iroju6rt.fsf@zoo.weinigel.se \
--to=christer@weinigel.se \
--cc=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