linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: Chuck Ebbert <cebbert@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: New format Intel microcode...
Date: Thu, 28 Jun 2007 10:29:06 -0700	[thread overview]
Message-ID: <4683EFE2.3040409@linux.intel.com> (raw)
In-Reply-To: <4683EF87.1050303@redhat.com>

Chuck Ebbert wrote:
> On 06/28/2007 10:12 AM, Arjan van de Ven wrote:
>> (while I work for Intel this is not an official Intel statement, but
>> there is so much FUD going around now that I feel I need to at least
>> point out a few things others "forget")
>>> Slashdot carried an article this morning saying that an error in Intel 
>>> microcode was being fixed.
>> don't just always believe everything you read on slashdot please
>>
>>>  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

that's a fedora bug; we asked them to update it long ago in their 
bugzilla. Maybe they updated the datafile, maybe they didn't. Be 
careful with just looking at package version numbers, they don't per 
se corresponds with versions of the data file.


> RHEL 5 has 1.15

be careful, it has the 1.17 datafile in the updates afaik.
but RH doesn't update the package version number.


same may or may not be true for the others, but if you only look at 
package versions you don't get the datafile versions.

  reply	other threads:[~2007-06-28 17:30 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 [this message]
2007-06-28 17:54             ` Daniel J Blueman
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=4683EFE2.3040409@linux.intel.com \
    --to=arjan@linux.intel.com \
    --cc=cebbert@redhat.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;
as well as URLs for NNTP newsgroup(s).