From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Bugs aren't features: X86_FEATURE_FXSAVE_LEAK
Date: Mon, 8 May 2006 10:47:58 -0700 (PDT) [thread overview]
Message-ID: <e3o08e$jm1$1@terminus.zytor.com> (raw)
In-Reply-To: 445CDED0.4070402@shaw.ca
Followup to: <445CDED0.4070402@shaw.ca>
By author: Robert Hancock <hancockr@shaw.ca>
In newsgroup: linux.dev.kernel
> >
> > 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.
>
> Point being, not this bug..
>
However, *MY* point is that we should have a uniform infrastructure
for bugs, just like we now have for features.
-hpa
next prev parent reply other threads:[~2006-05-08 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` Bugs aren't features: X86_FEATURE_FXSAVE_LEAK Robert Hancock
2006-05-08 17:47 ` H. Peter Anvin [this message]
2006-05-05 16:36 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
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='e3o08e$jm1$1@terminus.zytor.com' \
--to=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