[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQXGZYZiH3eUup2UXGWkeqKjsiHk7aMTFJO7xxFkqTpBZA@mail.gmail.com>
Date: Mon, 10 Dec 2012 18:39:39 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: "Yu, Fenghua" <fenghua.yu@...el.com>
Cc: "mingo@...nel.org" <mingo@...nel.org>,
"hpa@...or.com" <hpa@...or.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"hpa@...ux.intel.com" <hpa@...ux.intel.com>,
"linux-tip-commits@...r.kernel.org"
<linux-tip-commits@...r.kernel.org>
Subject: Re: [tip:x86/microcode] x86/microcode_intel_early.c: Early update
ucode on Intel's CPU
On Mon, Dec 3, 2012 at 4:18 PM, Yu, Fenghua <fenghua.yu@...el.com> wrote:
>> From: yhlu.kernel@...il.com [mailto:yhlu.kernel@...il.com] On Behalf Of
>> Yinghai Lu
>>
>> may need to copy the ucode.bin to BRK at first. that will make code
>> much simple, and later does not need to
>> copy them back in free_bootmem_initrd.
>>
>> aka, this patchset is not ready for 3.8 even.
>>
>
> I will relocate saved microcode blob (mc_saved_in_initrd) after initrd is
> relocated in updated patches. Thus, mc_saved_in_initrd always point to
> right initrd during boot time.
No, you should not copy that several times.
just pre-allocate some kbytes in BRK, and copy to there one time.
Yinghai
--
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