Re: [PATCH -v2 10/13] x86: Only direct map addresses that are marked as E820_RAM

2012-09-02 Thread Pekka Enberg
On Sun, Sep 2, 2012 at 10:46 AM, Yinghai Lu wrote: > From: Jacob Shin > > Currently direct mappings are created for [ 0 to max_low_pfn< and [ 4GB to max_pfn< backed by actual DRAM. This is fine for holes under 4GB which are covered > by fixed and variable range MTRRs to be UC. However, we run

[PATCH -v2 10/13] x86: Only direct map addresses that are marked as E820_RAM

2012-09-02 Thread Yinghai Lu
From: Jacob Shin Currently direct mappings are created for [ 0 to max_low_pfn< --- arch/x86/include/asm/page_types.h |8 +-- arch/x86/kernel/setup.c |8 ++- arch/x86/mm/init.c| 119 + arch/x86/mm/init_64.c |6

[PATCH -v2 10/13] x86: Only direct map addresses that are marked as E820_RAM

2012-09-02 Thread Yinghai Lu
From: Jacob Shin jacob.s...@amd.com Currently direct mappings are created for [ 0 to max_low_pfnPAGE_SHIFT ) and [ 4GB to max_pfnPAGE_SHIFT ), which may include regions that are not backed by actual DRAM. This is fine for holes under 4GB which are covered by fixed and variable range MTRRs to be

Re: [PATCH -v2 10/13] x86: Only direct map addresses that are marked as E820_RAM

2012-09-02 Thread Pekka Enberg
On Sun, Sep 2, 2012 at 10:46 AM, Yinghai Lu ying...@kernel.org wrote: From: Jacob Shin jacob.s...@amd.com Currently direct mappings are created for [ 0 to max_low_pfnPAGE_SHIFT ) and [ 4GB to max_pfnPAGE_SHIFT ), which may include regions that are not backed by actual DRAM. This is fine for