[PATCH 5/5] kexec: X86: Pass memory ranges via e820 table instead of memmap= boot parameter

H. Peter Anvin hpa at zytor.com
Mon Apr 15 10:49:13 EDT 2013


This is also true on some x86 systems.

Dave Hansen <dave at sr71.net> wrote:

>On 04/14/2013 09:52 PM, HATAYAMA Daisuke wrote:
>> This sounds like there's no such issue on x86 cache mechanism. Is it
>> correct? If so, what is the difference between ia64 and x86 cache
>> mechanisms?
>
>I'm just going by the code comments:
>
>drivers/char/mem.c
>>                 /*
>>                  * On ia64 if a page has been mapped somewhere as
>uncached, then
>>                  * it must also be accessed uncached by the kernel or
>data
>>                  * corruption may occur.
>>                  */

-- 
Sent from my mobile phone. Please excuse brevity and lack of formatting.



More information about the kexec mailing list