From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: 05e0caad3b7bd0d0fbeff980bca22f186241a501 breaks ia64 kdump
Date: Thu, 02 Nov 2006 08:29:09 +0000 [thread overview]
Message-ID: <20061102082907.GA18632@verge.net.au> (raw)
In-Reply-To: <20061026075951.GA30910@verge.net.au>
On Wed, Nov 01, 2006 at 09:38:38AM +0000, Mel Gorman wrote:
>
> Plan C
>
> Call add_active_ranges() for the the PFN ranges initmem reside in.
> Look at free_initmem() to see how to get the virtual address of the
> range is found and make the appropriate conversion. A variation is to
> call add_active_ranges() for the PFN range the whole kernel resides in
> if you have that information for the crash kernel.
I've made a version of this approach that seems to work.
I had to update add_active_range so that it merges
ranges that are not overlapping, but do create a continous range.
Is this a correct thing to do?
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
Index: linux-2.6/mm/page_alloc.c
=================================--- linux-2.6.orig/mm/page_alloc.c 2006-11-02 16:17:17.000000000 +0900
+++ linux-2.6/mm/page_alloc.c 2006-11-02 16:17:22.000000000 +0900
@@ -2407,7 +2407,7 @@
return;
/* Merge forward if suitable */
- if (start_pfn <= early_node_map[i].end_pfn &&
+ if (start_pfn <= early_node_map[i].end_pfn + 1 &&
end_pfn > early_node_map[i].end_pfn) {
early_node_map[i].end_pfn = end_pfn;
return;
@@ -2415,7 +2415,7 @@
/* Merge backward if suitable */
if (start_pfn < early_node_map[i].end_pfn &&
- end_pfn >= early_node_map[i].start_pfn) {
+ end_pfn + 1 >= early_node_map[i].start_pfn) {
early_node_map[i].start_pfn = start_pfn;
return;
}
Index: linux-2.6/arch/ia64/mm/discontig.c
=================================--- linux-2.6.orig/arch/ia64/mm/discontig.c 2006-11-02 16:17:59.000000000 +0900
+++ linux-2.6/arch/ia64/mm/discontig.c 2006-11-02 16:18:03.000000000 +0900
@@ -689,6 +689,8 @@
arch_sparse_init();
efi_memmap_walk(filter_rsvd_memory, count_node_pages);
+ add_active_range(0, ia64_tpa(_text) >> PAGE_SHIFT,
+ (ia64_tpa(_end) -1 ) >> PAGE_SHIFT);
#ifdef CONFIG_VIRTUAL_MEM_MAP
vmalloc_end -= PAGE_ALIGN(ALIGN(max_low_pfn, MAX_ORDER_NR_PAGES) *
next prev parent reply other threads:[~2006-11-02 8:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 7:59 05e0caad3b7bd0d0fbeff980bca22f186241a501 breaks ia64 kdump Horms
2006-10-26 13:27 ` Mel Gorman
2006-10-27 1:40 ` Zou, Nanhai
2006-10-27 2:30 ` Zou, Nanhai
2006-10-27 9:15 ` Andy Whitcroft
2006-10-30 0:55 ` Horms
2006-10-30 8:37 ` Horms
2006-10-30 9:11 ` Horms
2006-10-30 9:15 ` Horms
2006-10-30 9:25 ` Horms
2006-10-30 11:49 ` Mel Gorman
2006-10-31 3:29 ` Horms
2006-10-31 9:42 ` Mel Gorman
2006-11-02 8:24 ` Horms
2006-11-02 8:29 ` Horms [this message]
2006-11-02 9:32 ` Horms
2006-11-02 10:38 ` Zou, Nanhai
2006-11-02 16:26 ` Mel Gorman
2006-11-03 0:28 ` Zou, Nanhai
2006-11-03 1:19 ` Zou, Nanhai
2006-11-03 9:27 ` Mel Gorman
2006-11-03 10:06 ` Zou Nan hai
2006-11-03 10:23 ` Andy Whitcroft
2006-11-06 3:18 ` Horms
2006-11-06 3:26 ` Horms
2006-11-10 8:16 ` Zou, Nanhai
2006-11-10 11:47 ` Mel Gorman
2006-11-14 1:38 ` Zou, Nanhai
2006-11-14 23:42 ` Mel Gorman
2006-11-15 16:26 ` Mel Gorman
2006-11-16 6:26 ` Horms
2006-11-16 16:05 ` Mel Gorman
2006-11-20 1:40 ` Zou, Nanhai
2006-12-05 9:58 ` Christian Cotte-Barrot
2006-12-18 14:52 ` Mel Gorman
2006-12-19 0:28 ` Horms
2006-12-19 3:35 ` Horms
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061102082907.GA18632@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox