linux-kernel - Re: [tip:x86/microcode] x86/microcode_intel_early.c: Early update ucode on Intel's CPU

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 11 Dec 2012 10:02:20 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Borislav Petkov <bp@...en8.de>,
	"Yu, Fenghua" <fenghua.yu@...el.com>,
	"mingo@...nel.org" <mingo@...nel.org>,
	"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 12/11/2012 09:15 AM, Yinghai Lu wrote:
> On Tue, Dec 11, 2012 at 9:06 AM, Borislav Petkov <bp@...en8.de> wrote:
>> On Tue, Dec 11, 2012 at 09:00:55AM -0800, Yinghai Lu wrote:
>>> ok, then next question is how early it should be.
>>>
>>> before early_cpu_init/early_identify_cpu
>>>
>>> or just before check_bugs/identify_cpu
>>
>> Read the code. It's in x86_64_start_kernel on 64-bit.
>>
>
> No, that is not right place. initrd could be loaded anywhere like way
> high by bootloader.
>

The more I think about it, the more I think the right answer is the one 
we have pretty stated all along: if using the 64-bit entry point it is 
the responsibility of the boot loader to make sure the kernel, the setup 
data, and the initramfs are all mapped on entry.

	-hpa
-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
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/