[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6278d2220706281054m476873ffn32375725fe5c4f88@mail.gmail.com>
Date: Thu, 28 Jun 2007 18:54:29 +0100
From: "Daniel J Blueman" <daniel.blueman@...il.com>
To: "Chuck Ebbert" <cebbert@...hat.com>
Cc: "Arjan van de Ven" <arjan@...ux.intel.com>,
"Bill Davidsen" <davidsen@....com>,
"Andi Kleen" <andi@...stfloor.org>,
"Shaohua Li" <shaohua.li@...el.com>, jamagallon@....com,
tigran@...azian.fsnet.co.uk,
"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: New format Intel microcode...
On 28/06/07, Chuck Ebbert <cebbert@...hat.com> wrote:
> On 06/28/2007 10:12 AM, Arjan van de Ven wrote:
[snip]
> >> However, it listed only Windows related sites
> >> for the "fix" download. Is this the same TLB issue? And are these really
> >> fixes for Windows to flush the TLB properly the way Linux does?
> >
> > First of all, Linux has microcode updates as well. Some of the more
> > hypish news-bulletins just conveniently "forgot" about this. Basically
> > all distributions ship them, so users who use the distro update tools
> > get these automatically. And the update mentioned has been shipping for
> > a while (in version 1.17).
>
> Fedora 6 has version 1.13
> Fedora 7 also has 1.13
> RHEL 5 has 1.15
> Debian stable has 1.15 (9 Oct 2006)
> Suse 10.1 has 1.13
You've got to give credit to Intel for providing the ucode updates though.
The Ubuntu/Debian microcode.ctl package fetches a new version upon
installation/reconfiguration [1]; I guess if there were ucode updates
that resolved stability/vulnerability issues with Linux, the security
team could release an updated package with new default microcode.
However, I think the package isn't installed per default in Ubuntu
7.04 ia32/x86-64...
Daniel
--- [1]
# dpkg-reconfigure microcode.ctl
Local microcode is old, you need an update.
Trying to download an new version of microcode.
Now attempting to download microcode.
microcode downloaded sucessfully
--
Daniel J Blueman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists