Re: [tip:x86/microcode] x86/microcode_intel_early.c: Early updateucode on Intel's CPU

[H. Peter Anvin]

On 12/11/2012 11:18 AM, Yinghai Lu wrote:
> 
> that will be bunch of asm code again, and need to parse the setup_header in that
> asm to get range value for those regions...
> 

It's an index into an array, it's not "parsing".

>>
>>> but if the user memmap to exclude some page, we will still need to
>>> relocate the ramdisk.
>>
>> -ENOPARSE
> 
> .. I mean pointer for saved ucode will be updated then again.
> and relocated_initrd wil still need to use ioremap because init_memory_mapping
> will clean mapping the range range that is excluded by memmap=XX$YY
> 
>>
>> I really need to look at this in more detail.  I'm starting to think
>> this is done completely backwards.
> 
> really should not put asm code if it could be done in C in not complicated way.
> 

Uhm... that's not what I'm talking about.

	-hpa

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/