Fix parsing kernelcore boot option for ia64
Subsystems (5)
PATCH 1/1 Fix parsing kernelcore boot option for ia64
Hello.
cmdline_parse_kernelcore() should return the next pointer of boot option like memparse() doing. If not, it is cause of eternal loop on ia64 box. This patch is for 2.6.21-rc6-mm1.
----
arch/ia64/kernel/efi.c | 2 +- include/linux/mm.h | 2 +- mm/page_alloc.c | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-)
arch/ia64/kernel/efi.c +1 -1
@@ -424,7 +424,7 @@ efi_init (void) }else if (memcmp (cp,"max_addr=" ,9 ) ==0 ) { max_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); }else if (memcmp (cp,"kernelcore=" ,11 ) ==0 ) { -cmdline_parse_kernelcore (cp+11 ); +cmdline_parse_kernelcore (cp+11 , &cp); }else if (memcmp (cp,"min_addr=" ,9 ) ==0 ) { min_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); }else {
mm/page_alloc.c +2 -2
@@ -3736,13 +3736,13 @@ void __init free_area_init_nodes(unsigne* kernelcore=size sets the amount of memory for use for allocations that * cannot be reclaimed or migrated. */ -int __init cmdline_parse_kernelcore (char *p) +int __init cmdline_parse_kernelcore (char *p,char **retp) {unsigned long long coremem;if (!p)return -EINVAL ; - coremem =memparse (p, &p); + coremem =memparse (p, retp); required_kernelcore = coremem >>PAGE_SHIFT ;/* Paranoid check that UL is enough for required_kernelcore */
include/linux/mm.h +1 -1
@@ -1051,7 +1051,7 @@ extern unsigned long find_max_pfn_with_aextern void free_bootmem_with_active_regions (int nid,unsigned long max_low_pfn);extern void sparse_memory_present_with_active_regions (int nid); -extern int cmdline_parse_kernelcore (char *p); +extern int cmdline_parse_kernelcore (char *p,char **retp);#ifndef CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID extern int early_pfn_to_nid (unsigned long pfn);#endif /* CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID */
Signature · 1 line
Yasunori Goto
Quoted 8 lines · Yasunori Goto
Hello.
cmdline_parse_kernelcore()should return the next pointer of boot option likememparse()doing. If not, it is cause of eternal loop on ia64 box. This patch is for 2.6.21-rc6-mm1.Signed-off-by Yasunori Goto <[email protected]>
Andrew Morton
maintainerQuoted 54 lines · On Fri, 13 Apr 2007 14:26:22 +0900 Yasunori Goto <[email protected]> wrote:
Hello.
cmdline_parse_kernelcore()should return the next pointer of boot option likememparse()doing. If not, it is cause of eternal loop on ia64 box. This patch is for 2.6.21-rc6-mm1.Signed-off-by Yasunori Goto <[email protected]>----
arch/ia64/kernel/efi.c | 2 +- include/linux/mm.h | 2 +- mm/page_alloc.c | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-)Index:
current_test/arch/ia64/kernel/efi.c
===================================================================arch/ia64/kernel/efi.c +1
-1@@ -424,7 +424,7 @@ efi_init (void) }else if (memcmp (cp,"max_addr=" ,9 ) ==0 ) { max_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); }else if (memcmp (cp,"kernelcore=" ,11 ) ==0 ) { -cmdline_parse_kernelcore (cp+11 ); +cmdline_parse_kernelcore (cp+11 , &cp); }else if (memcmp (cp,"min_addr=" ,9 ) ==0 ) { min_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); }else {Index:
current_test/mm/page_alloc.c
===================================================================mm/page_alloc.c +2
-2@@ -3736,13 +3736,13 @@ void __init free_area_init_nodes(unsigne* kernelcore=size sets the amount of memory for use for allocations that * cannot be reclaimed or migrated. */ -int __init cmdline_parse_kernelcore (char *p) +int __init cmdline_parse_kernelcore (char *p,char **retp) {unsigned long long coremem;if (!p)return -EINVAL ; - coremem =memparse (p, &p); + coremem =memparse (p, retp); required_kernelcore = coremem >>PAGE_SHIFT ;/* Paranoid check that UL is enough for required_kernelcore */ Index:
current_test/include/linux/mm.h
===================================================================
include/linux/mm.h extern unsigned long find_max_pfn_with_a · line 1057
Quoted 8 lines
include/linux/mm.h +1
-1@@ -1051,7 +1051,7 @@ extern unsigned long find_max_pfn_with_aextern void free_bootmem_with_active_regions (int nid,unsigned long max_low_pfn);extern void sparse_memory_present_with_active_regions (int nid); -extern int cmdline_parse_kernelcore (char *p); +extern int cmdline_parse_kernelcore (char *p,char **retp);#ifndef CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID extern int early_pfn_to_nid (unsigned long pfn);#endif /* CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID */
This will cause all other architectures to crash when kernelcore= is used.
I wasn't even aware of this kernelcore thing. It's pretty nasty-looking. yet another reminder that this code hasn't been properly reviewed in the past year or three.
Quoted 67 lines · On Fri, 13 Apr 2007 14:26:22 +0900 Yasunori Goto <[email protected]> wrote:
Quoted 55 lines
Hello.
cmdline_parse_kernelcore()should return the next pointer of boot option likememparse()doing. If not, it is cause of eternal loop on ia64 box. This patch is for 2.6.21-rc6-mm1.Signed-off-by Yasunori Goto <[email protected]>----
arch/ia64/kernel/efi.c | 2 +- include/linux/mm.h | 2 +- mm/page_alloc.c | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-)Index:
current_test/arch/ia64/kernel/efi.c
===================================================================arch/ia64/kernel/efi.c +1
-1@@ -424,7 +424,7 @@ efi_init (void) }else if (memcmp (cp,"max_addr=" ,9 ) ==0 ) { max_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); }else if (memcmp (cp,"kernelcore=" ,11 ) ==0 ) { -cmdline_parse_kernelcore (cp+11 ); +cmdline_parse_kernelcore (cp+11 , &cp); }else if (memcmp (cp,"min_addr=" ,9 ) ==0 ) { min_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); }else {Index:
current_test/mm/page_alloc.c
===================================================================mm/page_alloc.c +2
-2@@ -3736,13 +3736,13 @@ void __init free_area_init_nodes(unsigne* kernelcore=size sets the amount of memory for use for allocations that * cannot be reclaimed or migrated. */ -int __init cmdline_parse_kernelcore (char *p) +int __init cmdline_parse_kernelcore (char *p,char **retp) {unsigned long long coremem;if (!p)return -EINVAL ; - coremem =memparse (p, &p); + coremem =memparse (p, retp); required_kernelcore = coremem >>PAGE_SHIFT ;/* Paranoid check that UL is enough for required_kernelcore */ Index:
current_test/include/linux/mm.h
===================================================================include/linux/mm.h extern unsigned long find_max_pfn_with_a · line 1057
Quoted 8 lines
include/linux/mm.h +1
-1@@ -1051,7 +1051,7 @@ extern unsigned long find_max_pfn_with_aextern void free_bootmem_with_active_regions (int nid,unsigned long max_low_pfn);extern void sparse_memory_present_with_active_regions (int nid); -extern int cmdline_parse_kernelcore (char *p); +extern int cmdline_parse_kernelcore (char *p,char **retp);#ifndef CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID extern int early_pfn_to_nid (unsigned long pfn);#endif /* CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID */ This will cause all other architectures to crash when kernelcore= is used.
Quoted 3 lines
I wasn't even aware of this kernelcore thing. It's pretty nasty-looking. yet another reminder that this code hasn't been properly reviewed in the past year or three.
Just now, I'm making memory-unplug patches with current MOVABLE_ZONE code. So, I might be the first user of it on ia64.
Anyway, I'll try to fix it.
Signature · 1 line
Yasunori Goto
Quoted 67 lines · Yasunori Goto
Quoted 67 lines · On Fri, 13 Apr 2007 14:26:22 +0900 Yasunori Goto <[email protected]> wrote:
Quoted 55 lines
Hello.
cmdline_parse_kernelcore()should return the next pointer of boot option likememparse()doing. If not, it is cause of eternal loop on ia64 box. This patch is for 2.6.21-rc6-mm1.Signed-off-by Yasunori Goto <[email protected]>----
arch/ia64/kernel/efi.c | 2 +- include/linux/mm.h | 2 +- mm/page_alloc.c | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-)Index:
current_test/arch/ia64/kernel/efi.c
===================================================================arch/ia64/kernel/efi.c +1
-1@@ -424,7 +424,7 @@ efi_init (void) }else if (memcmp (cp,"max_addr=" ,9 ) ==0 ) { max_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); }else if (memcmp (cp,"kernelcore=" ,11 ) ==0 ) { -cmdline_parse_kernelcore (cp+11 ); +cmdline_parse_kernelcore (cp+11 , &cp); }else if (memcmp (cp,"min_addr=" ,9 ) ==0 ) { min_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); }else {Index:
current_test/mm/page_alloc.c
===================================================================mm/page_alloc.c +2
-2@@ -3736,13 +3736,13 @@ void __init free_area_init_nodes(unsigne* kernelcore=size sets the amount of memory for use for allocations that * cannot be reclaimed or migrated. */ -int __init cmdline_parse_kernelcore (char *p) +int __init cmdline_parse_kernelcore (char *p,char **retp) {unsigned long long coremem;if (!p)return -EINVAL ; - coremem =memparse (p, &p); + coremem =memparse (p, retp); required_kernelcore = coremem >>PAGE_SHIFT ;/* Paranoid check that UL is enough for required_kernelcore */ Index:
current_test/include/linux/mm.h
===================================================================include/linux/mm.h extern unsigned long find_max_pfn_with_a · line 1057
Quoted 8 lines
include/linux/mm.h +1
-1@@ -1051,7 +1051,7 @@ extern unsigned long find_max_pfn_with_aextern void free_bootmem_with_active_regions (int nid,unsigned long max_low_pfn);extern void sparse_memory_present_with_active_regions (int nid); -extern int cmdline_parse_kernelcore (char *p); +extern int cmdline_parse_kernelcore (char *p,char **retp);#ifndef CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID extern int early_pfn_to_nid (unsigned long pfn);#endif /* CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID */ This will cause all other architectures to crash when kernelcore= is used.
Quoted 9 lines
Quoted 3 lines
I wasn't even aware of this kernelcore thing. It's pretty nasty-looking. yet another reminder that this code hasn't been properly reviewed in the past year or three.
Just now, I'm making memory-unplug patches with current
MOVABLE_ZONEcode. So, I might be the first user of it on ia64.Anyway, I'll try to fix it.
I'm looking at this as well. There may be more than one problem in there so I'm being more thorough with testing on other arches.
Andrew, the option is part of the zone-based solution to fragmentation avoidance which hasn't been mentioned in a while. That's probably why it fell off your radar. It's nasty looking because sizing the portion of memory usable by any allocation so that it is evenly spread throughout all nodes is not trivial. I think that having mem= parsing broken on NUMA at various times in the past (and probably still broken) highlights that.
Signature · 3 lines
Mel Gorman Part-time Phd Student Linux Technology Center University of Limerick IBM Dublin Software Lab
Quoted 9 lines
Quoted 3 lines
I wasn't even aware of this kernelcore thing. It's pretty nasty-looking. yet another reminder that this code hasn't been properly reviewed in the past year or three.
Just now, I'm making memory-unplug patches with current
MOVABLE_ZONEcode. So, I might be the first user of it on ia64.Anyway, I'll try to fix it.
Can you review this patch and see does it fix the problem please? There was a second problem that showed up while testing this in relation to the bootmem allocator assumptions about zone boundary alignment. I'll follow up this mail with the patch in case you are seeing that problem.
Subject: Fix parsing kernelcore boot option V2 cmdline_parse_kernelcore() should return the next pointer of boot option like memparse() doing. If not, it is cause of eternal loop on ia64 box. This patch is for 2.6.21-rc6-mm1. This patch changes the kernelcore command line parsing so that is compatible with both early_param() way of doing things and IA64.
arch/i386/kernel/setup.c +1 -1
@@ -195,7 +195,7 @@ static int __init parse_mem(char *arg)return 0 ; }early_param ("mem" , parse_mem); -early_param ("kernelcore" , cmdline_parse_kernelcore); +early_param ("kernelcore" , early_parse_kernelcore);#ifdef CONFIG_PROC_VMCORE /* elfcorehdr= specifies the location of elf core header
arch/ia64/kernel/efi.c +1 -1
@@ -423,7 +423,7 @@ efi_init (void) }else if (memcmp (cp,"max_addr=" ,9 ) ==0 ) { max_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); }else if (memcmp (cp,"kernelcore=" ,11 ) ==0 ) { -cmdline_parse_kernelcore (cp+11 ); +parse_kernelcore (cp+11 , &cp); }else if (memcmp (cp,"min_addr=" ,9 ) ==0 ) { min_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); }else {
arch/powerpc/kernel/prom.c +1 -1
@@ -431,7 +431,7 @@ static int __init early_parse_mem(char *return 0 ; }early_param ("mem" , early_parse_mem); -early_param ("kernelcore" , cmdline_parse_kernelcore); +early_param ("kernelcore" , early_parse_kernelcore);/* * The device tree may be allocated below our memory limit, or inside the
arch/ppc/mm/init.c +1 -1
@@ -214,7 +214,7 @@ void MMU_setup(void) } } -early_param ("kernelcore" , cmdline_parse_kernelcore); +early_param ("kernelcore" , early_parse_kernelcore);/* * MMU_init sets up the basic memory mappings for the kernel,
arch/x86_64/kernel/e820.c +1 -1
@@ -604,7 +604,7 @@ static int __init parse_memopt(char *p)return 0 ; }early_param ("mem" , parse_memopt); -early_param ("kernelcore" , cmdline_parse_kernelcore); +early_param ("kernelcore" , early_parse_kernelcore);static int userdef__initdata ;
include/linux/mm.h +2 -1
@@ -1051,7 +1051,8 @@ extern unsigned long find_max_pfn_with_aextern void free_bootmem_with_active_regions (int nid,unsigned long max_low_pfn);extern void sparse_memory_present_with_active_regions (int nid); -extern int cmdline_parse_kernelcore (char *p); +extern int parse_kernelcore (char *p,char **retp); +extern int early_parse_kernelcore (char *p);#ifndef CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID extern int early_pfn_to_nid (unsigned long pfn);#endif /* CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID */
mm/page_alloc.c +8 -2
@@ -3728,13 +3728,13 @@ void __init free_area_init_nodes(unsigne* kernelcore=size sets the amount of memory for use for allocations that * cannot be reclaimed or migrated. */ -int __init cmdline_parse_kernelcore (char *p) +int __init parse_kernelcore (char *p,char **retp) {unsigned long long coremem;if (!p)return -EINVAL ; - coremem =memparse (p, &p); + coremem =memparse (p, retp); required_kernelcore = coremem >>PAGE_SHIFT ;/* Paranoid check that UL is enough for required_kernelcore */
@@ -3742,6 +3742,12 @@ int __init cmdline_parse_kernelcore(char return 0; } + +/* For use with early_param where available */ +int __init early_parse_kernelcore (char *p) +{ +return parse_kernelcore (p, &p); +}#endif /* CONFIG_ARCH_POPULATES_NODE_MAP */ /**
On (23/04/07 19:32), Mel Gorman didst pronounce:
Quoted 5 lines
There
was a second problem that showed up while testing this in relation to the bootmem allocator assumptions about zone boundary alignment. I'll follow up this mail with the patch in case you are seeing that problem.
Tony Luck added to cc list as I believe he had a lot to do with the speed improvements within the bootmem allocator and might suggest a better fix.
Subject: Check zone boundaries when freeing bootmem
Zone boundaries do not have to be aligned to MAX_ORDER_NR_PAGES. However, during boot, there is an implicit assumption that they are aligned to a BITS_PER_LONG boundary when freeing pages as quickly as possible. This patch checks the zone boundaries when freeing pages from the bootmem allocator.
mm/bootmem.c +11 -7
@@ -302,13 +302,15 @@ found:static unsigned long __init free_all_bootmem_core (pg_data_t *pgdat) { -struct page *page; +struct page *page =NULL , *end_page =NULL ;unsigned long pfn;bootmem_data_t *bdata = pgdat->bdata;unsigned long i, count, total =0 ;unsigned long idx;unsigned long *map;int gofast =0 ; +int gofast_order =ffs (BITS_PER_LONG ) -1 ; +int gofast_size =1 << gofast_order;BUG_ON (!bdata->node_bootmem_map);
@@ -324,19 +326,21 @@ static unsigned long __init free_all_boofor (i =0 ; i < idx; ) {unsigned long v = ~map[i /BITS_PER_LONG ]; -if (gofast && v == ~0UL ) { -int order; - +if (v) { page =pfn_to_page (pfn); + end_page = page + gofast_size -1 ; + } + +/* Do not cross zone boundaries when fast freeing */ +if (gofast && v == ~0UL && +page_zone_id (page) ==page_zone_id (end_page)) { count +=BITS_PER_LONG ; - order =ffs (BITS_PER_LONG ) -1 ; -__free_pages_bootmem (page, order); +__free_pages_bootmem (page, gofast_order); i +=BITS_PER_LONG ; page +=BITS_PER_LONG ; }else if (v) {unsigned long m; - page =pfn_to_page (pfn);for (m =1 ; m && i < idx; m<<=1 , page++, i++) {if (v & m) { count++;
Quoted 4 lines
Subject: Check zone boundaries when freeing bootmem Zone boundaries do not have to be aligned to
MAX_ORDER_NR_PAGES.
Hmm. I don't understand here yet... Could you explain more?
This issue occurs only when ZONE_MOVABLE is specified. If its boundary is aligned to MAX_ORDER automatically, I guess user will not mind it.
Quoted 1 line
From memory hotplug view, I prefer section size alignment to make
simple code. :-P
Quoted 4 lines
However,
during boot, there is an implicit assumption that they are aligned to aBITS_PER_LONGboundary when freeing pages as quickly as possible. This patch checks the zone boundaries when freeing pages from the bootmem allocator.
Anyway, the patch works well.
Bye.
Signature · 1 line
Yasunori Goto
Quoted 7 lines · Yasunori Goto
Quoted 4 lines
Subject: Check zone boundaries when freeing bootmem Zone boundaries do not have to be aligned to
MAX_ORDER_NR_PAGES.Hmm. I don't understand here yet... Could you explain more?
Nodes are required to be MAX_ORDER_NR_PAGES aligned for the buddy algorithm to work but zones can be at any alignment because the page_is_buddy() check checks the zone_id of two buddies when merging. As zones are generally aligned anyway, it was never noticed that the bootmem allocators assumes zones are at least order-5 aligned on 32 bit and order-6 aligned on 64 bit.
Quoted 1 line
This issue occurs only when
ZONE_MOVABLEis specified.
Yes, because it can be sized to any value. At the moment, zones are aligned to MAX_ORDER_NR_PAGES so it was not noticed that bootmem makes assumptions on zone alignment.
Quoted 3 lines
If its boundary is aligned to
MAX_ORDERautomatically, I guess user will not mind it.
Probably not. They will get a different amount of memory usable by the kernel than they asked for but it doesn't really matter. Huge pages generally need MAX_ORDER_NR_PAGES base pages as well so the alignment doesn't hurt there.
Quoted 3 lines
From memory hotplug view, I prefer section size alignment to make simple code. :-P
That's fair. I'll roll up a patch that aligns to MAX_ORDER_NR_PAGES to begin with and then decide if it should align to section size on SPARSEMEM or not.
Quoted 8 lines
Quoted 5 lines
However,
during boot, there is an implicit assumption that they are aligned to aBITS_PER_LONGboundary when freeing pages as quickly as possible. This patch checks the zone boundaries when freeing pages from the bootmem allocator.Anyway, the patch works well.
Right, I'll resend it to linux-mm as a standalone patch later so because it fixes a correctness issue albeit one that is easily avoided.
Quoted 2 lines
Bye.
Thanks
Signature · 3 lines
Mel Gorman Part-time Phd Student Linux Technology Center University of Limerick IBM Dublin Software Lab
On (24/04/07 18:58), Yasunori Goto didst pronounce:
Quoted 5 lines
Quoted 4 lines
Subject: Check zone boundaries when freeing bootmem Zone boundaries do not have to be aligned to
MAX_ORDER_NR_PAGES.
Quoted 8 lines
Hmm. I don't understand here yet... Could you explain more?
This issue occurs only when
ZONE_MOVABLEis specified. If its boundary is aligned toMAX_ORDERautomatically, I guess user will not mind it.From memory hotplug view, I prefer section size alignment to make simple code. :-P
How does this look to you?
======
The two potential users of ZONE_MOVABLE would prefer if the zone was aligned to a boundary. This patch aligns the zone to a MAX_ORDER_NR_PAGES boundary.
mm/page_alloc.c +5 -0
@@ -3642,6 +3642,11 @@ restart: usable_nodes--;if (usable_nodes && required_kernelcore > usable_nodes) goto restart; + +/* Align start of ZONE_MOVABLE on all nids to MAX_ORDER_NR_PAGES */ +for (nid =0 ; nid <MAX_NUMNODES ; nid++) + zone_movable_pfn[nid] = +roundup (zone_movable_pfn[nid],MAX_ORDER_NR_PAGES ); }/**
Signature · 3 lines
Mel Gorman Part-time Phd Student Linux Technology Center University of Limerick IBM Dublin Software Lab
Quoted 15 lines · On Mon, 23 Apr 2007 19:32:46 +0100 [email protected] (Mel Gorman) wrote:
Quoted 9 lines
Quoted 3 lines
I wasn't even aware of this kernelcore thing. It's pretty nasty-looking. yet another reminder that this code hasn't been properly reviewed in the past year or three.
Just now, I'm making memory-unplug patches with current
MOVABLE_ZONEcode. So, I might be the first user of it on ia64.Anyway, I'll try to fix it.
Can you review this patch and see does it fix the problem please? There was a second problem that showed up while testing this in relation to the bootmem allocator assumptions about zone boundary alignment. I'll follow up this mail with the patch in case you are seeing that problem.
Quoted 7 lines
Subject: Fix parsing kernelcore boot option V2
cmdline_parse_kernelcore()should return the next pointer of boot option likememparse()doing. If not, it is cause of eternal loop on ia64 box. This patch is for 2.6.21-rc6-mm1. This patch changes the kernelcore command line parsing so that is compatible with bothearly_param()way of doing things and IA64.
In my understanding, why ia64 doesn't use early_param() macro for mem= at el. is that it has to use mem= option at efi handling which is called before parse_early_param().
Current ia64's boot path is
setup_arch()
-> efi handling -> parse_early_param() -> numa handling -> pgdat/zone init
kernelcore= option is just used at pgdat/zone initialization. (no arch dependent part...)
So I think just adding
== early_param("kernelcore",cmpdline_parse_kernelcore) ==
to ia64 is ok.....
-Kame
Mel-san.
I tested your patch (Thanks!). It worked. But......
Quoted 7 lines
In my understanding, why ia64 doesn't use
early_param()macro for mem= at el. is that it has to use mem= option at efi handling which is called beforeparse_early_param().Current ia64's boot path is
setup_arch()-> efi handling -> parse_early_param() -> numa handling -> pgdat/zone init
Quoted 7 lines
kernelcore= option is just used at pgdat/zone initialization. (no arch dependent part...)
So I think just adding
==early_param("kernelcore",cmpdline_parse_kernelcore)==
to ia64 is ok.....
Then, it can be common code.
How is this patch? I confirmed this can work well too.
--------
When "kernelcore" boot option is specified, kernel can't boot up on ia64. It is cause of eternal loop.
In addition, its code can be common code. This is fix for it. I tested this patch on my ia64 box.
---------
arch/i386/kernel/setup.c | 1 - arch/ia64/kernel/efi.c | 2 -- arch/powerpc/kernel/prom.c | 1 - arch/ppc/mm/init.c | 2 -- arch/x86_64/kernel/e820.c | 1 - include/linux/mm.h | 1 - mm/page_alloc.c | 3 +++ 7 files changed, 3 insertions(+), 8 deletions(-)
arch/ia64/kernel/efi.c +0 -2
@@ -423,8 +423,6 @@ efi_init (void) mem_limit =memparse (cp +4 , &cp); }else if (memcmp (cp,"max_addr=" ,9 ) ==0 ) { max_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); - }else if (memcmp (cp,"kernelcore=" ,11 ) ==0 ) { -cmdline_parse_kernelcore (cp+11 ); }else if (memcmp (cp,"min_addr=" ,9 ) ==0 ) { min_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); }else {
arch/i386/kernel/setup.c +0 -1
@@ -195,7 +195,6 @@ static int __init parse_mem(char *arg)return 0 ; }early_param ("mem" , parse_mem); -early_param ("kernelcore" , cmdline_parse_kernelcore);#ifdef CONFIG_PROC_VMCORE /* elfcorehdr= specifies the location of elf core header
arch/powerpc/kernel/prom.c +0 -1
@@ -431,7 +431,6 @@ static int __init early_parse_mem(char *return 0 ; }early_param ("mem" , early_parse_mem); -early_param ("kernelcore" , cmdline_parse_kernelcore);/* * The device tree may be allocated below our memory limit, or inside the
arch/ppc/mm/init.c +0 -2
@@ -214,8 +214,6 @@ void MMU_setup(void) } } -early_param ("kernelcore" , cmdline_parse_kernelcore); -/* * MMU_init sets up the basic memory mappings for the kernel, * including both RAM and possibly some I/O regions,
arch/x86_64/kernel/e820.c +0 -1
@@ -604,7 +604,6 @@ static int __init parse_memopt(char *p)return 0 ; }early_param ("mem" , parse_memopt); -early_param ("kernelcore" , cmdline_parse_kernelcore);static int userdef__initdata ;
include/linux/mm.h +0 -1
@@ -1051,7 +1051,6 @@ extern unsigned long find_max_pfn_with_aextern void free_bootmem_with_active_regions (int nid,unsigned long max_low_pfn);extern void sparse_memory_present_with_active_regions (int nid); -extern int cmdline_parse_kernelcore (char *p);#ifndef CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID extern int early_pfn_to_nid (unsigned long pfn);#endif /* CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID */
mm/page_alloc.c +3 -0
@@ -3728,6 +3728,9 @@ int __init cmdline_parse_kernelcore(char return 0; } + +early_param ("kernelcore" , cmdline_parse_kernelcore); +#endif /* CONFIG_ARCH_POPULATES_NODE_MAP */ /**
Signature · 1 line
Yasunori Goto
Mel Gorman
Acked-byOn (24/04/07 16:31), Yasunori Goto didst pronounce:
Quoted 18 lines
Mel-san.
I tested your patch (Thanks!). It worked. But......
Quoted 14 lines
In my understanding, why ia64 doesn't use
early_param()macro for mem= at el. is that it has to use mem= option at efi handling which is called beforeparse_early_param().Current ia64's boot path is
setup_arch()-> efi handling -> parse_early_param() -> numa handling -> pgdat/zone initkernelcore= option is just used at pgdat/zone initialization. (no arch dependent part...)
So I think just adding
==early_param("kernelcore",cmpdline_parse_kernelcore)==
to ia64 is ok.....
It should be ok. I had missed that IA64 supports early_param now and handling this in common code makes sense.
Quoted 4 lines
Then, it can be common code.
How is this patch? I confirmed this can work well too.
This worked fine from a command-line perspective on most test machines. In combination with the align-zone_movable-to-maxordernrpages-boundary patch, x86_64, ppc64 and IA64 test machines all booted successfully with and without kernelcore= specified.
I'll resend the two relevant patches for this problem with an explanation leader mail and cc linux-mm. Thanks for helping sort this out.
Quoted 114 lines
--------
When "kernelcore" boot option is specified, kernel can't boot up on ia64. It is cause of eternal loop.
In addition, its code can be common code. This is fix for it. I tested this patch on my ia64 box.Signed-off-by Yasunori Goto <[email protected]>---------
arch/i386/kernel/setup.c | 1 - arch/ia64/kernel/efi.c | 2 -- arch/powerpc/kernel/prom.c | 1 - arch/ppc/mm/init.c | 2 -- arch/x86_64/kernel/e820.c | 1 - include/linux/mm.h | 1 - mm/page_alloc.c | 3 +++ 7 files changed, 3 insertions(+), 8 deletions(-)Index:
kernelcore/arch/ia64/kernel/efi.c
===================================================================arch/ia64/kernel/efi.c +0
-2@@ -423,8 +423,6 @@ efi_init (void) mem_limit =memparse (cp +4 , &cp); }else if (memcmp (cp,"max_addr=" ,9 ) ==0 ) { max_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); - }else if (memcmp (cp,"kernelcore=" ,11 ) ==0 ) { -cmdline_parse_kernelcore (cp+11 ); }else if (memcmp (cp,"min_addr=" ,9 ) ==0 ) { min_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); }else {Index:
kernelcore/arch/i386/kernel/setup.c
===================================================================arch/i386/kernel/setup.c +0
-1@@ -195,7 +195,6 @@ static int __init parse_mem(char *arg)return 0 ; }early_param ("mem" , parse_mem); -early_param ("kernelcore" , cmdline_parse_kernelcore);#ifdef CONFIG_PROC_VMCORE /* elfcorehdr= specifies the location of elf core header Index:
kernelcore/arch/powerpc/kernel/prom.c
===================================================================arch/powerpc/kernel/prom.c +0
-1@@ -431,7 +431,6 @@ static int __init early_parse_mem(char *return 0 ; }early_param ("mem" , early_parse_mem); -early_param ("kernelcore" , cmdline_parse_kernelcore);/* * The device tree may be allocated below our memory limit, or inside the Index:
kernelcore/arch/ppc/mm/init.c
===================================================================arch/ppc/mm/init.c +0
-2@@ -214,8 +214,6 @@ void MMU_setup(void) } } -early_param ("kernelcore" , cmdline_parse_kernelcore); -/* * MMU_init sets up the basic memory mappings for the kernel, * including both RAM and possibly some I/O regions, Index:
kernelcore/arch/x86_64/kernel/e820.c
===================================================================arch/x86_64/kernel/e820.c +0
-1@@ -604,7 +604,6 @@ static int __init parse_memopt(char *p)return 0 ; }early_param ("mem" , parse_memopt); -early_param ("kernelcore" , cmdline_parse_kernelcore);static int userdef__initdata ;Index:
kernelcore/include/linux/mm.h
===================================================================include/linux/mm.h +0
-1@@ -1051,7 +1051,6 @@ extern unsigned long find_max_pfn_with_aextern void free_bootmem_with_active_regions (int nid,unsigned long max_low_pfn);extern void sparse_memory_present_with_active_regions (int nid); -extern int cmdline_parse_kernelcore (char *p);#ifndef CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID extern int early_pfn_to_nid (unsigned long pfn);#endif /* CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID */ Index:
kernelcore/mm/page_alloc.c
===================================================================mm/page_alloc.c +3
-0@@ -3728,6 +3728,9 @@ int __init cmdline_parse_kernelcore(char return 0; } + +early_param ("kernelcore" , cmdline_parse_kernelcore); +#endif /* CONFIG_ARCH_POPULATES_NODE_MAP */ /** Signature · 2 lines
-- Yasunori Goto
Signature · 4 lines
-- Mel Gorman Part-time Phd Student Linux Technology Center University of Limerick IBM Dublin Software Lab