public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Bugs aren't features: X86_FEATURE_FXSAVE_LEAK
Date: Tue, 09 May 2006 10:38:02 -0400	[thread overview]
Message-ID: <4460A94A.10905@tmr.com> (raw)
In-Reply-To: <p733bfo5ol1.fsf@bragg.suse.de>

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.
> 
The initial argument is dead on, bugs should be either presented as a
"fixed" feature, or there could (should?) be a bugs vector which could
be or'd. It's at least possible that AMD might fix this some time.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me



  parent reply	other threads:[~2006-05-09 14:40 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
2006-05-09 14:38   ` Bill Davidsen [this message]
     [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=4460A94A.10905@tmr.com \
    --to=davidsen@tmr.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