forked from Minki/linux
[PATCH] V5 ia64 SPARSEMEM - eliminate contig_page_data
For FLATMEM contig_page_data has been made transparent to the arch code. This patch conforms to that change. Signed-off-by: Bob Picco <bob.picco@hp.com> Signed-off-by: Tony Luck <tony.luck@intel.com>
This commit is contained in:
parent
da9577c531
commit
c678796cab
@ -269,7 +269,7 @@ paging_init (void)
|
||||
efi_memmap_walk(find_largest_hole, (u64 *)&max_gap);
|
||||
if (max_gap < LARGE_GAP) {
|
||||
vmem_map = (struct page *) 0;
|
||||
free_area_init_node(0, &contig_page_data, zones_size, 0,
|
||||
free_area_init_node(0, NODE_DATA(0), zones_size, 0,
|
||||
zholes_size);
|
||||
} else {
|
||||
unsigned long map_size;
|
||||
@ -282,7 +282,7 @@ paging_init (void)
|
||||
efi_memmap_walk(create_mem_map_page_table, NULL);
|
||||
|
||||
NODE_DATA(0)->node_mem_map = vmem_map;
|
||||
free_area_init_node(0, &contig_page_data, zones_size,
|
||||
free_area_init_node(0, NODE_DATA(0), zones_size,
|
||||
0, zholes_size);
|
||||
|
||||
printk("Virtual mem_map starts at 0x%p\n", mem_map);
|
||||
|
Loading…
Reference in New Issue
Block a user