RE: 05e0caad3b7bd0d0fbeff980bca22f186241a501 breaks ia64 kdump

From: Zou, Nanhai <nanhai.zou_at_intel.com>
Date: 2006-11-03 12:19:24
> -----Original Message-----
> From: linux-ia64-owner@vger.kernel.org
> [mailto:linux-ia64-owner@vger.kernel.org] On Behalf Of Zou, Nanhai
> Sent: 2006113 8:29
> To: Mel Gorman; Horms
> Cc: Andy Whitcroft; linux-ia64@vger.kernel.org; Bob Picco; Andrew Morton; Dave
> Hansen; Andi Kleen; Benjamin Herrenschmidt; Paul Mackerras; Keith Mannthey;
> Luck, Tony; KAMEZAWA Hiroyuki; Yasunori Goto; Khalid Aziz
> Subject: RE: 05e0caad3b7bd0d0fbeff980bca22f186241a501 breaks ia64 kdump
> 
> Hi,
> 	This patch should fix the issue.
> 
> Thanks
> Zou Nan hai

Some description of the issue,
	When ia64 kernel is configured as discontinuous memory model, 
active_pages are added through efi_memmap_walk(filter_rsvd_memory, count_node_pages). 
filter_rsvd_memory  will filter out all regions in rsvd_regions include 
- boot param
- mem map
- initrd
- command line
- **** kernel code and data ***
- kernel map built from efi memmap
- crash kernel reserved region
So the kernel code and data is excluded even without kdump support,
check /proc/iomem and dmesg for early_node_data can verify that.
But magically, the first kernel boots happily without any complain...,
I guess that is related to the init value in memmap. 

This patch use another filter to add_acvitive_pages, only exclude crash kernel reserved region if CONFIG_KEXEC is on.

However I am still not understand what the start = OREDERROUNDDOWN(start) in cound_node_page is used for, it round up mem_data[node].min_pfn to a very huge alignment.
I guess we can get rid of this by not using filter_rsvd_memory to call count_node_pages.

Thanks
Zou Nan hai









-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Fri Nov 03 12:20:24 2006

This archive was generated by hypermail 2.1.8 : 2006-11-03 12:20:37 EST