LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Bill Davidsen <davidsen@tmr.com>,
Andi Kleen <andi@firstfloor.org>,
Daniel J Blueman <daniel.blueman@gmail.com>,
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 13:27:35 -0400 [thread overview]
Message-ID: <4683EF87.1050303@redhat.com> (raw)
In-Reply-To: <1183039975.14676.12.camel@laptopd505.fenrus.org>
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
RHEL 5 has 1.15
Debian stable has 1.15 (9 Oct 2006)
Suse 10.1 has 1.13
next prev parent reply other threads:[~2007-06-28 17:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 23:45 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 [this message]
2007-06-28 17:29 ` Arjan van de Ven
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=4683EF87.1050303@redhat.com \
--to=cebbert@redhat.com \
--cc=andi@firstfloor.org \
--cc=arjan@linux.intel.com \
--cc=daniel.blueman@gmail.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 \
--subject='Re: New format Intel microcode...' \
/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
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).