[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4683BD56.7070707@tmr.com>
Date: Thu, 28 Jun 2007 09:53:26 -0400
From: Bill Davidsen <davidsen@....com>
To: Andi Kleen <andi@...stfloor.org>
CC: Daniel J Blueman <daniel.blueman@...il.com>,
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...
Andi Kleen wrote:
> "Daniel J Blueman" <daniel.blueman@...il.com> writes:
>
>> On 23/03/07, Shaohua Li <shaohua.li@...el.com> wrote:
>>> On Thu, 2007-03-22 at 23:45 +0000, Daniel J Blueman wrote:
>>>> Hi Shao-hua,
>>>>
>>>> Is the tool you mentioned last June [1] available for splitting up the
>>>> old firmware files to the new format (eg
>>>> /lib/firmware/intel-ucode/06-0d-06), or are updates available from
>>>> Intel (or otherwise) in this new format?
>>> Yes, we are preparing the new format data files and maybe put it into a
>>> new website. We will announce it when it's ready.
>> It's been a while; is there any sign of the ucode updates being
>> available, especially in light of the C2D/Q incorrect TLB invalidation
>> + recent ucode to fix this?
>
> That microcode update is not needed on any recent Linux kernel; it flushes
> the TLBs in a way that is fine.
>
Slashdot carried an article this morning saying that an error in Intel
microcode was being fixed. 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?
--
Bill Davidsen <davidsen@....com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
-
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