[IA64] fix the difference between node_mem_map and node_start_pfn
authorKen'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>
Wed, 29 Oct 2008 21:17:57 +0000 (14:17 -0700)
committerTony Luck <tony.luck@intel.com>
Tue, 4 Nov 2008 19:31:12 +0000 (11:31 -0800)
commitaca14f33104bb7b101df23cdd36c520b7c66bcfd
tree1c17323cf1fdf334103696449b2a22a90c937ed2
parentd6e15199d1784df90b7535e625f7617bd343d202
[IA64] fix the difference between node_mem_map and node_start_pfn

makedumpfile[1] cannot run on ia64 discontigmem kernel, because the member
node_mem_map of struct pgdat_list has invalid value.  This patch fixes it.

node_start_pfn shows the start pfn of each node, and node_mem_map should
point 'struct page' of each node's node_start_pfn.  On my machine, node0's
node_start_pfn shows 0x400 and its node_mem_map points 0xa0007fffbf000000.
 This address is the same as vmem_map, so the node_mem_map points 'struct
page' of pfn 0, even if its node_start_pfn shows 0x400.

The cause is due to the round down of min_pfn in count_node_pages() and
node0's node_mem_map points 'struct page' of inactive pfn (0x0).  This
patch fixes it.

makedumpfile[1]: dump filtering command
https://sourceforge.net/projects/makedumpfile/

Signed-off-by: Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>
Cc: Bernhard Walle <bwalle@suse.de>
Cc: Jay Lan <jlan@sgi.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Tony Luck <tony.luck@intel.com>
arch/ia64/include/asm/meminit.h
arch/ia64/mm/discontig.c