From: Mikael Pettersson <mikpe@csd.uu.se>
To: tigran@veritas.com
Cc: dr@bofh.de, linux-kernel@vger.kernel.org,
richard.schaal@intel.com, torvalds@transmeta.com
Subject: Re: Linux-2.4.0-test10
Date: Wed, 1 Nov 2000 13:51:55 +0100 (MET) [thread overview]
Message-ID: <200011011251.NAA24041@harpo.it.uu.se> (raw)
On Wed, 1 Nov 2000, Tigran Aivazian wrote:
>But it contains an erroneous part in microcode.c:
>
>- if (c->x86_vendor != X86_VENDOR_INTEL || c->x86 < 6){
>+ if (c->x86_vendor != X86_VENDOR_INTEL || c->x86 != 6){
> printk(KERN_ERR "microcode: CPU%d not an Intel P6\n",
>cpu_num);
>
>
>It was not in Daniel's cleanup patch which I saw but came from elsewhere.
>Are there Intel CPUs with family>6 which do not support the same mechanism
>for microcode update as family=6? The manuals suggest that test for ">" is
>correct, i.e. that Intel will maintain compatibility with P6 wrt microcode
>update.
The patch came from me, as part of the patch kit to make the kernel
safe(r) for the Pentium IV processor. There were several places
which made unwarranted assumptions about ->x86 not exceeding 6, and
they would break since Pentium IV has family 15.
[Reading #243192 ...]
Concerning the microcode update driver, I cannot find anything in
the IA32-Vol3 manual to suggest it is not P6 specific.
The Pentium IV is not a P6, hence the stricter test.
Of course, this should be reviewed once the PentiumIV-updated
IA32-Vol3 manual has been released.
You say the manuals suggest testing for family >= 6.
Exactly which manual does that, and where?
(But I should have passed the patch to you Tigran before Linus.
Mea culpa, but it seemed such an obvious bug&fix ...)
/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-01 12:54 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-01 12:51 Mikael Pettersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-02 18:46 Linux-2.4.0-test10 CRADOCK, Christopher
2000-11-02 0:03 Linux-2.4.0-test10 Jeff Garzik
2000-10-31 20:41 ` Linux-2.4.0-test10 Linus Torvalds
2000-10-31 20:48 ` Linux-2.4.0-test10 Rik van Riel
2000-10-31 20:57 ` Linux-2.4.0-test10 Linus Torvalds
2000-11-01 5:40 ` Linux-2.4.0-test10 adrian
2000-10-31 20:55 ` Linux-2.4.0-test10 Alan Cox
2000-11-01 1:35 ` Linux-2.4.0-test10 Paul Jakma
2000-11-01 3:53 ` Linux-2.4.0-test10 Jeremy Fitzhardinge
2000-11-01 8:38 ` Linux-2.4.0-test10 Andi Kleen
2000-11-01 18:08 ` Linux-2.4.0-test10 kuznet
2000-11-01 23:52 ` Linux-2.4.0-test10 David S. Miller
2000-11-02 17:17 ` Linux-2.4.0-test10 Stephen C. Tweedie
2000-11-02 17:36 ` Linux-2.4.0-test10 Christoph Rohland
2000-11-03 19:18 ` Linux-2.4.0-test10 Pavel Machek
2000-11-04 18:49 ` Linux-2.4.0-test10 Marco d'Itri
2000-11-05 1:44 ` Linux-2.4.0-test10 H. Peter Anvin
2000-11-06 12:55 ` Linux-2.4.0-test10 Stephen C. Tweedie
2000-11-09 16:45 ` Linux-2.4.0-test10 Stephen C. Tweedie
2000-11-01 2:18 ` Linux-2.4.0-test10 Tom Rini
2000-11-01 5:46 ` Linux-2.4.0-test10 Miles Lane
2000-11-01 5:43 ` Linux-2.4.0-test10 Linus Torvalds
2000-11-01 10:19 ` Linux-2.4.0-test10 Tigran Aivazian
2000-11-01 15:01 ` Linux-2.4.0-test10 Alan Cox
2000-11-01 15:19 ` Linux-2.4.0-test10 Tigran Aivazian
2000-11-01 16:12 Linux-2.4.0-test10 CRADOCK, Christopher
2000-11-02 0:44 ` Linux-2.4.0-test10 M.H.VanLeeuwen
2000-11-02 17:57 ` Linux-2.4.0-test10 Ragnar Hojland Espinosa
2000-11-02 18:38 ` Linux-2.4.0-test10 Ragnar Hojland Espinosa
2000-11-03 6:25 ` Linux-2.4.0-test10 kernel
2000-11-03 10:02 ` Linux-2.4.0-test10 Ben Ford
2000-11-07 10:22 ` Linux-2.4.0-test10 Ragnar Hojland Espinosa
2000-11-07 18:39 ` Linux-2.4.0-test10 Zephaniah E. Hull
2000-11-03 7:08 ` Linux-2.4.0-test10 James Simmons
2000-11-01 6:03 Linux-2.4.0-test10 M.H.VanLeeuwen
2000-11-01 19:28 ` Linux-2.4.0-test10 David Ford
2000-11-02 0:08 ` Linux-2.4.0-test10 M.H.VanLeeuwen
2000-11-02 2:57 ` Linux-2.4.0-test10 David Ford
2000-11-02 7:15 ` Linux-2.4.0-test10 Vitezslav Samel
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=200011011251.NAA24041@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=dr@bofh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.schaal@intel.com \
--cc=tigran@veritas.com \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®