RE: [Xen-devel] 2.6.32.27 dom0 + latest xen staging boot failure

[Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>]

On Wed, 16 Feb 2011, Kay, Allen M wrote:
> Setting max_pfn_mapped here has no effect.  It still fails the same way.
> 
> Later on in setup_arch(), max_pfn_mapped is set to max_lower_pfn_mapped.  For 
> 64 bit dom0, it will try to set it again for memory above 4GB by calling 
> init_memory_mapping(1UL<<32, max_pfn<<PAGE_SHIFT) - this is where it 
> eventually fails.
> 

It shouldn't make any difference what value max_pfn_mapped holds at that
point. It mattered before because it changes the way the memory for the
initial page table is allocated (see
arch/x86/mm/init.c:find_early_table_space).

> The problem is max_pfn also contains non-RAM extra memory.  Should max_pfn 
> set to xen_low_pfn_mapped before calling init_memory_mapping for memory above 
> 4GB?
> 

that shouldn't be a problem because it is marked as reserved in
xen_add_extra_mem, so it shouldn't be used to store the pagetable pages
(or anything else really).

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel