linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel J Blueman" <daniel.blueman@gmail.com>
To: "Chuck Ebbert" <cebbert@redhat.com>
Cc: "Arjan van de Ven" <arjan@linux.intel.com>,
	"Bill Davidsen" <davidsen@tmr.com>,
	"Andi Kleen" <andi@firstfloor.org>,
	"Shaohua Li" <shaohua.li@intel.com>,
	jamagallon@ono.com, tigran@aivazian.fsnet.co.uk,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: New format Intel microcode...
Date: Thu, 28 Jun 2007 18:54:29 +0100	[thread overview]
Message-ID: <6278d2220706281054m476873ffn32375725fe5c4f88@mail.gmail.com> (raw)
In-Reply-To: <4683EF87.1050303@redhat.com>

On 28/06/07, Chuck Ebbert <cebbert@redhat.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

  parent reply	other threads:[~2007-06-28 17:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 23:45 New format Intel microcode Daniel J Blueman
2007-03-23  0:43 ` Shaohua Li
2007-03-23  9:43   ` Marcel Holtmann
2007-03-23  9:03     ` Arjan van de Ven
2007-03-26  8:34       ` Marcel Holtmann
2007-03-26  8:52         ` Arjan van de Ven
2007-06-26 21:42   ` Daniel J Blueman
2007-06-26 23:29     ` Andi Kleen
2007-06-28 13:53       ` Bill Davidsen
2007-06-28 14:12         ` Arjan van de Ven
2007-06-28 15:48           ` Alex Riesen
2007-06-28 17:27           ` Chuck Ebbert
2007-06-28 17:29             ` Arjan van de Ven
2007-06-28 17:54             ` Daniel J Blueman [this message]
2007-06-28 15:27         ` Andi Kleen
2007-06-28 15:44           ` Chuck Ebbert
2007-06-28 22:55             ` Bill Davidsen
2007-06-28 22:23           ` Bill Davidsen
2007-06-28 22:30             ` Arjan van de Ven
2007-06-28 23:09             ` Andi Kleen
2007-07-02  8:56   ` Alex Riesen
2007-07-02 17:18     ` Arjan van de Ven
2007-07-02 18:22       ` Alex Riesen

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=6278d2220706281054m476873ffn32375725fe5c4f88@mail.gmail.com \
    --to=daniel.blueman@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=arjan@linux.intel.com \
    --cc=cebbert@redhat.com \
    --cc=davidsen@tmr.com \
    --cc=jamagallon@ono.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=tigran@aivazian.fsnet.co.uk \
    /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;
as well as URLs for NNTP newsgroup(s).