Re: [PATCH V2 0/5] x86: Create direct mappings for E820_RAM only

2012-08-14 Thread WANG Chao
On 08/15/2012 06:54 AM, Jacob Shin wrote: On Tue, Aug 14, 2012 at 04:34:39PM +0800, Dave Young wrote: On 08/14/2012 05:46 AM, Jacob Shin wrote: Currently kernel direct mappings are created for all pfns between [ 0 to max_low_pfn ) and [ 4GB to max_pfn ). When we introduce memory holes, we end

Re: [PATCH V2 0/5] x86: Create direct mappings for E820_RAM only

2012-08-14 Thread Jacob Shin
On Tue, Aug 14, 2012 at 04:34:39PM +0800, Dave Young wrote: > On 08/14/2012 05:46 AM, Jacob Shin wrote: > > > Currently kernel direct mappings are created for all pfns between > > [ 0 to max_low_pfn ) and [ 4GB to max_pfn ). When we introduce memory > > holes, we end up mapping memory ranges that

Re: [PATCH V2 0/5] x86: Create direct mappings for E820_RAM only

2012-08-14 Thread Dave Young
On 08/14/2012 04:34 PM, Dave Young wrote: > On 08/14/2012 05:46 AM, Jacob Shin wrote: > >> Currently kernel direct mappings are created for all pfns between >> [ 0 to max_low_pfn ) and [ 4GB to max_pfn ). When we introduce memory >> holes, we end up mapping memory ranges that are not backed by ph

Re: [PATCH V2 0/5] x86: Create direct mappings for E820_RAM only

2012-08-14 Thread Dave Young
On 08/14/2012 05:46 AM, Jacob Shin wrote: > Currently kernel direct mappings are created for all pfns between > [ 0 to max_low_pfn ) and [ 4GB to max_pfn ). When we introduce memory > holes, we end up mapping memory ranges that are not backed by physical > DRAM. This is fine for lower memory addre

[PATCH V2 0/5] x86: Create direct mappings for E820_RAM only

2012-08-13 Thread Jacob Shin
Currently kernel direct mappings are created for all pfns between [ 0 to max_low_pfn ) and [ 4GB to max_pfn ). When we introduce memory holes, we end up mapping memory ranges that are not backed by physical DRAM. This is fine for lower memory addresses which can be marked as UC by fixed/variable ra