Fix sparsemem on Cell
Subsystems (7)
PATCH 1/1 Fix sparsemem on Cell
I think the comments added say it pretty well, but I'll repeat it here.
This fix is pretty similar in concept to the one that Arnd posted as a temporary workaround, but I've added a few comments explaining what the actual assumptions are, and improved it a wee little bit.
The end goal here is to simply avoid calling the early_*() functions when it is _not_ early. Those functions stop working as soon as free_initmem() is called. system_state is set to SYSTEM_RUNNING just after free_initmem() is called, so it seems appropriate to use here.
I did think twice about actually using SYSTEM_RUNNING because we moved away from it in other parts of memory hotplug, but those were actually for _allocations_ in favor of slab_is_available(), and we really don't care about the slab here.
The only other assumption is that all memory-hotplug-time pages given to memmap_init_zone() are valid and able to be onlined into any any zone after the system is running. The "valid" part is really just a question of whether or not a 'struct page' is there for the pfn, and *not* whether there is actual memory. Since all sparsemem sections have contiguous mem_map[]s within them, and we only memory hotplug entire sparsemem sections, we can be confident that this assumption will hold.
As for the memory being in the right node, we'll assume tha memory hotplug is putting things in the right node.
---
lxc-dave/init/main.c | 4 ++++ lxc-dave/mm/page_alloc.c | 28 +++++++++++++++++++++++++--- 2 files changed, 29 insertions(+), 3 deletions(-)
init/main.c renamed from init/main.c~sparsemem-fix +4 -0
@@ -770,6 +770,10 @@ static int init(void * unused)free_initmem ();unlock_kernel ();mark_rodata_ro (); +/* +* Memory hotplug requires that this system_state transition +* happer after free_initmem(). (see memmap_init_zone()) +*/ system_state =SYSTEM_RUNNING ;numa_default_policy ();
mm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-fix +25 -3
@@ -2056,6 +2056,30 @@ static inline unsigned long wait_table_b#define LONG_ALIGN (x) (((x)+(sizeof(long))-1)&~((sizeof(long))-1)) +static int can_online_pfn_into_nid (unsigned long pfn,int nid) +{ +/* +* There are two things that make this work: +* 1. The early_pfn...() functions are __init and +* use __initdata. If the system is < SYSTEM_RUNNING, +* those functions and their data will still exist. +* 2. We also assume that all actual memory hotplug +* (as opposed to boot-time) calls to this are only +* for contiguous memory regions. With sparsemem, +* this guaranteed is easy because all sections are +* contiguous and we never online more than one +* section at a time. Boot-time memory can have holes +* anywhere. +*/ +if (system_state >=SYSTEM_RUNNING ) +return 1 ; +if (!early_pfn_valid (pfn)) +return 0 ; +if (!early_pfn_in_nid (pfn, nid)) +return 0 ; +return 1 ; +} +/* * Initially all pages are reserved - free ones are freed * up by free_all_bootmem() once the early boot process is
@@ -2069,9 +2093,7 @@ void __meminit memmap_init_zone(unsignedunsigned long pfn;for (pfn = start_pfn; pfn < end_pfn; pfn++) { -if (!early_pfn_valid (pfn)) -continue ; -if (!early_pfn_in_nid (pfn, nid)) +if (!can_online_pfn_into_nid (pfn))continue ; page =pfn_to_page (pfn);set_page_links (page, zone, nid, pfn);
_
Quoted 17 lines · Dave Hansen
I think the comments added say it pretty well, but I'll repeat it here.
This fix is pretty similar in concept to the one that Arnd posted as a temporary workaround, but I've added a few comments explaining what the actual assumptions are, and improved it a wee little bit.
The end goal here is to simply avoid calling the early_*() functions when it is _not_ early. Those functions stop working as soon as
free_initmem()is called.system_stateis set toSYSTEM_RUNNINGjust afterfree_initmem()is called, so it seems appropriate to use here.I did think twice about actually using
SYSTEM_RUNNINGbecause we moved away from it in other parts of memory hotplug, but those were actually for _allocations_ in favor ofslab_is_available(), and we really don't care about the slab here.
Quoted 7 lines
The only other assumption is that all memory-hotplug-time pages given to
memmap_init_zone()are valid and able to be onlined into any any zone after the system is running. The "valid" part is
really just a question of whether or not a 'struct page' is there
for the pfn, and *not* whether there is actual memory. Since
all sparsemem sections have contiguous mem_map[]s within them,
and we only memory hotplug entire sparsemem sections, we can
be confident that this assumption will hold.
ie. that if hotplug is pushing this memory into a zone on a node it really does know what its doing, and its putting it in the right place.
Obviously that code needs to be 'overlap' aware but thats ok for this
interface.
Quoted 16 lines
As for the memory being in the right node, we'll assume tha memory hotplug is putting things in the right node.
Signed-off-by Dave Hansen <[email protected]>---
lxc-dave/init/main.c | 4 ++++ lxc-dave/mm/page_alloc.c | 28 +++++++++++++++++++++++++--- 2 files changed, 29 insertions(+), 3 deletions(-)diff -puN
init/main.c~sparsemem-fixinit/main.c
init/main.c static int init(void * unused) · line 776
Quoted 7 lines
init/main.c renamed from init/main.c~sparsemem-fix +4
-0@@ -770,6 +770,10 @@ static int init(void * unused)free_initmem ();unlock_kernel ();mark_rodata_ro (); +/* +* Memory hotplug requires that this system_state transition +* happer after free_initmem(). (see memmap_init_zone()) +*/
typo: happen
mm/page_alloc.c static inline unsigned long wait_table_b · line 2060
Quoted 12 lines
init/main.c renamed from init/main.c~sparsemem-fix +0
-0system_state =SYSTEM_RUNNING ;numa_default_policy ();diff -puN
mm/page_alloc.c~sparsemem-fixmm/page_alloc.cmm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-fix +2
-0@@ -2056,6 +2056,30 @@ static inline unsigned long wait_table_b#define LONG_ALIGN (x) (((x)+(sizeof(long))-1)&~((sizeof(long))-1)) +static int can_online_pfn_into_nid (unsigned long pfn,int nid) +{
__meminit ?
Quoted 5 lines
mm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-fix +5
-0+/* +* There are two things that make this work: +* 1. The early_pfn...() functions are __init and +* use __initdata. If the system is < SYSTEM_RUNNING, +* those functions and their data will still exist.
mm/page_alloc.c static inline unsigned long wait_table_b · line 2075
Quoted 10 lines
mm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-fix +10
-0+* 2. We also assume that all actual memory hotplug +* (as opposed to boot-time) calls to this are only +* for contiguous memory regions. With sparsemem, +* this guaranteed is easy because all sections are +* contiguous and we never online more than one +* section at a time. Boot-time memory can have holes +* anywhere. +*/ +if (system_state >=SYSTEM_RUNNING ) +return 1 ;
Is there any value in codifying the assumption here, as a safety net?
if (system_state >= SYSTEM_RUNNING)
#ifdef CONFIG_SPARSEMEM return 1; #else return 0;
#endif
Quoted 11 lines
mm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-fix +7
-0+if (!early_pfn_valid (pfn)) +return 0 ; +if (!early_pfn_in_nid (pfn, nid)) +return 0 ; +return 1 ; +} +/* * Initially all pages are reserved - free ones are freed * up by free_all_bootmem() once the early boot process is
mm/page_alloc.c void __meminit memmap_init_zone(unsigned · line 2096
Quoted 7 lines
mm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-fix +1
-3@@ -2069,9 +2093,7 @@ void __meminit memmap_init_zone(unsignedunsigned long pfn;for (pfn = start_pfn; pfn < end_pfn; pfn++) { -if (!early_pfn_valid (pfn)) -continue ; -if (!early_pfn_in_nid (pfn, nid)) +if (!can_online_pfn_into_nid (pfn))
We're not passing nid here?
Quoted 4 lines
mm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-fix +0
-0continue ; page =pfn_to_page (pfn);set_page_links (page, zone, nid, pfn);_
Looks like this would do the job to me.
-apw
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 4 lines · Andy Whitcroft
ie. that if hotplug is pushing this memory into a zone on a node it really does know what its doing, and its putting it in the right place.
Obviously that code needs to be 'overlap' aware but thats ok for this
interface.
I'm not sure if this, especially if we're only doing one section at a time.
Quoted 8 lines
Quoted 8 lines
(quoted diff) +0
-0system_state = SYSTEM_RUNNING; numa_default_policy();diff -puN
mm/page_alloc.c~sparsemem-fixmm/page_alloc.cmm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-fix +0
-0@@ -2056,6 +2056,30 @@ static inline unsigned long wait_table_b
Quoted 6 lines
mm/page_alloc.c static inline unsigned long wait_table_b · line 2060
Quoted 4 lines
mm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-fix +2
-0#define LONG_ALIGN (x) (((x)+(sizeof(long))-1)&~((sizeof(long))-1)) +static int can_online_pfn_into_nid (unsigned long pfn,int nid) +{
__meminit?
Yup. I'll get that.
Quoted 18 lines
Quoted 5 lines
mm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-fix +5
-0+/* +* There are two things that make this work: +* 1. The early_pfn...() functions are __init and +* use __initdata. If the system is < SYSTEM_RUNNING, +* those functions and their data will still exist. mm/page_alloc.c static inline unsigned long wait_table_b · line 2075
Quoted 10 lines
mm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-fix +10
-0+* 2. We also assume that all actual memory hotplug +* (as opposed to boot-time) calls to this are only +* for contiguous memory regions. With sparsemem, +* this guaranteed is easy because all sections are +* contiguous and we never online more than one +* section at a time. Boot-time memory can have holes +* anywhere. +*/ +if (system_state >=SYSTEM_RUNNING ) +return 1 ;Is there any value in codifying the assumption here, as a safety net?
Quoted 6 lines
if (
system_state>=SYSTEM_RUNNING)#ifdef CONFIG_SPARSEMEM return 1; #else return 0;#endif
Dunno. The normal case is that it isn't even called without memory hotplug. The only non-sparsemem memory hotplug is Keith's baby, and they lay out all of their mem_map at boot-time anyway, so I don't think this gets used.
Keith, do you know whether you even do memmap_init_zone() at runtime, and if you ever have holes if/when you do?
Quoted 13 lines
Quoted 13 lines
mm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-fix +7
-0+if (!early_pfn_valid (pfn)) +return 0 ; +if (!early_pfn_in_nid (pfn, nid)) +return 0 ; +return 1 ; +} +/* * Initially all pages are reserved - free ones are freed * up by free_all_bootmem() once the early boot process is @@ -2069,9 +2093,7 @@ void __meminit memmap_init_zone(unsignedunsigned long pfn;
Quoted 7 lines
mm/page_alloc.c void __meminit memmap_init_zone(unsigned · line 2096
Quoted 5 lines
mm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-fix +1
-3for (pfn = start_pfn; pfn < end_pfn; pfn++) { -if (!early_pfn_valid (pfn)) -continue ; -if (!early_pfn_in_nid (pfn, nid)) +if (!can_online_pfn_into_nid (pfn))We're not passing nid here?
No, because my ppc64 cross compiler has magically broken. :(
Fixed patch appended.
-- Dave
I think the comments added say it pretty well, but I'll repeat it here.
This fix is pretty similar in concept to the one that Arnd posted as a temporary workaround, but I've added a few comments explaining what the actual assumptions are, and improved it a wee little bit.
The end goal here is to simply avoid calling the early_*() functions when it is _not_ early. Those functions stop working as soon as free_initmem() is called. system_state is set to SYSTEM_RUNNING just after free_initmem() is called, so it seems appropriate to use here.
I did think twice about actually using SYSTEM_RUNNING because we moved away from it in other parts of memory hotplug, but those were actually for _allocations_ in favor of slab_is_available(), and we really don't care about the slab here.
The only other assumption is that all memory-hotplug-time pages given to memmap_init_zone() are valid and able to be onlined into any any zone after the system is running. The "valid" part is really just a question of whether or not a 'struct page' is there for the pfn, and *not* whether there is actual memory. Since all sparsemem sections have contiguous mem_map[]s within them, and we only memory hotplug entire sparsemem sections, we can be confident that this assumption will hold.
As for the memory being in the right node, we'll assume tha memory hotplug is putting things in the right node.
---
lxc-dave/init/main.c | 4 ++++ lxc-dave/mm/page_alloc.c | 28 +++++++++++++++++++++++++--- 2 files changed, 29 insertions(+), 3 deletions(-)
init/main.c renamed from init/main.c~sparsemem-fix +4 -0
@@ -770,6 +770,10 @@ static int init(void * unused)free_initmem ();unlock_kernel ();mark_rodata_ro (); +/* +* Memory hotplug requires that this system_state transition +* happen after free_initmem(). (see memmap_init_zone()) +*/ system_state =SYSTEM_RUNNING ;numa_default_policy ();
mm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-fix +25 -3
@@ -2056,6 +2056,30 @@ static inline unsigned long wait_table_b#define LONG_ALIGN (x) (((x)+(sizeof(long))-1)&~((sizeof(long))-1)) +static int __meminit can_online_pfn_into_nid (unsigned long pfn,int nid) +{ +/* +* There are two things that make this work: +* 1. The early_pfn...() functions are __init and +* use __initdata. If the system is < SYSTEM_RUNNING, +* those functions and their data will still exist. +* 2. We also assume that all actual memory hotplug +* (as opposed to boot-time) calls to this are only +* for contiguous memory regions. With sparsemem, +* this guaranteed is easy because all sections are +* contiguous and we never online more than one +* section at a time. Boot-time memory can have holes +* anywhere. +*/ +if (system_state >=SYSTEM_RUNNING ) +return 1 ; +if (!early_pfn_valid (pfn)) +return 0 ; +if (!early_pfn_in_nid (pfn, nid)) +return 0 ; +return 1 ; +} +/* * Initially all pages are reserved - free ones are freed * up by free_all_bootmem() once the early boot process is
@@ -2069,9 +2093,7 @@ void __meminit memmap_init_zone(unsignedunsigned long pfn;for (pfn = start_pfn; pfn < end_pfn; pfn++) { -if (!early_pfn_valid (pfn)) -continue ; -if (!early_pfn_in_nid (pfn, nid)) +if (!can_online_pfn_into_nid (pfn, nid))continue ; page =pfn_to_page (pfn);set_page_links (page, zone, nid, pfn);
_
Quoted 9 lines · On Fri, 15 Dec 2006 09:24:00 -0800 Dave Hansen <[email protected]> wrote:
...
I think the comments added say it pretty well, but I'll repeat it here.
This fix is pretty similar in concept to the one that Arnd posted as a temporary workaround, but I've added a few comments explaining what the actual assumptions are, and improved it a wee little bit.
Quoted 5 lines
The end goal here is to simply avoid calling the early_*() functions when it is _not_ early. Those functions stop working as soon as
free_initmem()is called.system_stateis set toSYSTEM_RUNNINGjust afterfree_initmem()is called, so it seems appropriate to use here.
Would really prefer not to do this. system_state is evil. Its semantics are poorly-defined and if someone changes them a bit, or changes memory initialisation order, you get whacked.
I think an mm-private flag with /*documented*/ semantics would be better. It's only a byte.
Quoted 1 line
+static int
__meminitcan_online_pfn_into_nid(unsigned long pfn, int nid)
I spent some time trying to work out what "can_online_pfn_into_nid" can possibly mean and failed. "We can bring a pfn online then turn it into a NID"? Don't think so. "We can bring this page online and allocate it to this node"? Maybe.
Perhaps if the function's role in the world was commented it would be clearer.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 2 lines · On Fri, 15 Dec 2006 11:45:36 -0800 Andrew Morton <[email protected]> wrote:
Perhaps if the function's role in the world was commented it would be clearer.
How about patch like this ? (this one is not tested.) Already-exisiting-more-generic-flag is available ?
-Kame
==
include/linux/memory_hotplug.h | 8 ++++++++ mm/memory_hotplug.c | 14 ++++++++++++++ mm/page_alloc.c | 11 +++++++---- 3 files changed, 29 insertions(+), 4 deletions(-)
include/linux/memory_hotplug.h +8 -0
@@ -133,6 +133,10 @@#endif /* CONFIG_NUMA */ #endif /* CONFIG_HAVE_ARCH_NODEDATA_EXTENSION */ +extern int under_memory_hotadd (void ); + + +#else /* ! CONFIG_MEMORY_HOTPLUG */ /* * Stub functions for when hotplug is off
@@ -159,6 +163,10 @@dump_stack ();return -ENOSYS ; } +static inline int under_memory_hotadd () +{ +return 0 ; +}#endif /* ! CONFIG_MEMORY_HOTPLUG */ static inline int __remove_pages(struct zone *zone, unsigned long start_pfn,
mm/memory_hotplug.c +14 -0
@@ -26,6 +26,17 @@#include <asm/tlbflush.h> +/* +* Because memory hotplug shares some codes for initilization with boot, +* we sometimes have to check what we are doing ? +*/ +static atomic_t memory_hotadd_count; + +int under_memory_hotadd (void ) +{ +return atomic_read (&memory_hotadd_count); +} +/* add this memory to iomem resource */ static struct resource *register_memory_resource (u64 start,u64 size) {
@@ -273,10 +284,13 @@if (ret) goto error; } +atomic_inc (&memory_hotadd_count);/* call arch's memory hotadd */ ret =arch_add_memory (nid, start, size); +atomic_dec (&memory_hotadd_count); +if (ret <0 ) goto error;
mm/page_alloc.c +7 -4
@@ -2069,10 +2069,13 @@unsigned long pfn;for (pfn = start_pfn; pfn < end_pfn; pfn++) { -if (!early_pfn_valid (pfn)) -continue ; -if (!early_pfn_in_nid (pfn, nid)) -continue ; +if (!under_memory_hotadd ()) { +/* we are in boot */ +if (!early_pfn_valid (pfn)) +continue ; +if (!early_pfn_in_nid (pfn, nid)) +continue ; + } page =pfn_to_page (pfn);set_page_links (page, zone, nid, pfn);init_page_count (page);
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
mm/memory_hotplug.c line 292
Quoted 13 lines · KAMEZAWA Hiroyuki
/* add this memory to iomem resource */
static struct resource *register_memory_resource(u64 start, u64 size) {mm/memory_hotplug.c +2
-0@@ -273,10 +284,13 @@if (ret) goto error; } +atomic_inc (&memory_hotadd_count);/* call arch's memory hotadd */ ret =arch_add_memory (nid, start, size); +atomic_dec (&memory_hotadd_count);
I'd be willing to be that this will work just fine. But, I think we can do it without any static state at all, if we just pass a runtime-or-not flag down into the arch_add_memory() call chain.
I'll code that up so we can compare to yours.
-- Dave
Quoted 13 lines · Dave Hansen
Quoted 12 lines · KAMEZAWA Hiroyuki
/* add this memory to iomem resource */
static struct resource *register_memory_resource(u64 start, u64 size) {mm/memory_hotplug.c +1
-0@@ -273,10 +284,13 @@if (ret) goto error; } +atomic_inc (&memory_hotadd_count);/* call arch's memory hotadd */ ret =arch_add_memory (nid, start, size);
Quoted 7 lines
mm/memory_hotplug.c line 292
Quoted 1 line
mm/memory_hotplug.c +1
-0+atomic_dec (&memory_hotadd_count);I'd be willing to be that this will work just fine. But, I think we can do it without any static state at all, if we just pass a runtime-or-not flag down into the
arch_add_memory()call chain.I'll code that up so we can compare to yours.
Yes, I stronly concur that passing an explicit flag is much much better than any hack involving global state.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 4 lines · KAMEZAWA Hiroyuki
(quoted diff) +0
-0@@ -273,10 +284,13 @@ if (ret) goto error; }
Review line 296
Quoted 10 lines
(quoted diff) +3
-0+ atomic_inc(&memory_hotadd_count); /* call arch's memory hotadd */ ret = arch_add_memory(nid, start, size); + atomic_dec(&memory_hotadd_count); + if (ret < 0) goto error;
This also doesn't fix the problem on cell, since the time when the bug happens, we're not calling through this function, or arch_add_memory, at all, but rather invoke __add_pages directly. As BenH already mentioned, we shouldn't do really call __add_pages at all.
Let me attempt another fix that might address all cases. This is completely untested as of now, but also addresses Dave's latest comment.
Arnd <><
arch/ia64/mm/init.c +1 -1
@@ -543,7 +543,7 @@ virtual_memmap_init (u64 start, u64 end, void *arg)if (map_start < map_end)memmap_init_zone ((unsigned long )(map_end - map_start), - args->nid, args->zone,page_to_pfn (map_start)); + args->nid, args->zone,page_to_pfn (map_start),1 );return 0 ; }
arch/s390/mm/vmem.c +1 -1
@@ -61,7 +61,7 @@ void memmap_init(unsigned long size, int nid, unsigned long zone,if (map_start < map_end)memmap_init_zone ((unsigned long )(map_end - map_start), - nid, zone,page_to_pfn (map_start)); + nid, zone,page_to_pfn (map_start),1 ); } }
include/linux/mm.h +1 -1
@@ -978,7 +978,7 @@ extern int early_pfn_to_nid(unsigned long pfn);#endif /* CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID */ #endif /* CONFIG_ARCH_POPULATES_NODE_MAP */ extern void set_dma_reserve (unsigned long new_dma_reserve); -extern void memmap_init_zone (unsigned long ,int ,unsigned long ,unsigned long ); +extern void memmap_init_zone (unsigned long ,int ,unsigned long ,unsigned long ,int );extern void setup_per_zone_pages_min (void );extern void mem_init (void );extern void show_mem (void );
mm/memory_hotplug.c +1 -1
@@ -71,7 +71,7 @@ static int __add_zone(struct zone *zone, unsigned long phys_start_pfn)if (ret <0 )return ret; } -memmap_init_zone (nr_pages, nid, zone_type, phys_start_pfn); +memmap_init_zone (nr_pages, nid, zone_type, phys_start_pfn,0 );return 0 ; }
mm/page_alloc.c +8 -6
@@ -1953,17 +1953,19 @@ static inline unsigned long wait_table_bits(unsigned long size)* done. Non-atomic initialization, single-pass. */ void __meminit memmap_init_zone (unsigned long size,int nid,unsigned long zone, -unsigned long start_pfn) +unsigned long start_pfn,int early) {struct page *page;unsigned long end_pfn = start_pfn + size;unsigned long pfn;for (pfn = start_pfn; pfn < end_pfn; pfn++) { -if (!early_pfn_valid (pfn)) -continue ; -if (!early_pfn_in_nid (pfn, nid)) -continue ; +if (early) { +if (!early_pfn_valid (pfn)) +continue ; +if (!early_pfn_in_nid (pfn, nid)) +continue ; + } page =pfn_to_page (pfn);set_page_links (page, zone, nid, pfn);init_page_count (page);
@@ -1990,7 +1992,7 @@ void zone_init_free_lists(struct pglist_data *pgdat, struct zone *zone,#ifndef __HAVE_ARCH_MEMMAP_INIT#define memmap_init (size, nid, zone, start_pfn) \ - memmap_init_zone((size), (nid), (zone), (start_pfn)) + memmap_init_zone((size), (nid), (zone), (start_pfn), 1)#endif static int __cpuinit zone_batchsize (struct zone *zone)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
mm/page_alloc.c void zone_init_free_lists(struct pglist_data *pgdat, struct zone *zone, · line 1996
Quoted 5 lines · Arnd Bergmann
#ifndef
__HAVE_ARCH_MEMMAP_INIT
#definememmap_init(size, nid, zone, start_pfn)\mm/page_alloc.c +1
-1- memmap_init_zone((size), (nid), (zone), (start_pfn)) + memmap_init_zone((size), (nid), (zone), (start_pfn), 1)#endif
This is what I was thinking of. Sometimes I find these kinds of calls a bit annoying:
foo(0, 1, 1, 0, 99, 22)
It only takes a minute to look up what all of the numbers do, but that is one minute too many. :)
How about an enum, or a pair of #defines?
enum context
{
EARLY,
HOTPLUG
};
extern void memmap_init_zone(unsigned long, int, unsigned long, unsigned long,
enum call_context);
...
So, the call I quoted above would become:
memmap_init_zone((size), (nid), (zone), (start_pfn), EARLY)
-- Dave
Quoted 5 lines · On Mon, 18 Dec 2006 15:16:20 -0800 Dave Hansen <[email protected]> wrote:
enum context
{
EARLY,
HOTPLUG
};
I like this :)
Thanks,
-Kame
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 7 lines · Dave Hansen
How about an enum, or a pair of #defines?
enum context
{
EARLY,
HOTPLUG
};
Sounds good, but since this is in a global header file, it needs to be in an appropriate name space, like
enum memmap_context {
MEMMAP_EARLY,
MEMMAP_HOTPLUG,
};
Arnd <><
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Pulling cbe... list off the cc because it is giving annoying 'too many recipients' warnings.
Quoted 8 lines · Arnd Bergmann
Quoted 7 lines · Dave Hansen
How about an enum, or a pair of #defines?
enum context
{
EARLY,
HOTPLUG
};
This patch should do the trick. Arnd, can you try this to make sure it solves the issue? Also, if you get a chance, could you do a quick s390 boot of it? It was the only arch touched by this whole thing.
It compiles on all of my i386 .configs.
--
The following patch fixes an oops experienced on the Cell architecture when init-time functions, early_*(), are called at runtime. It alters the call paths to make sure that the callers explicitly say whether the call is being made on behalf of a hotplug even, or happening at boot-time.
---
lxc-dave/arch/s390/mm/vmem.c | 3 ++- lxc-dave/include/linux/mm.h | 7 ++++++- lxc-dave/include/linux/mmzone.h | 3 ++- lxc-dave/mm/memory_hotplug.c | 6 ++++-- lxc-dave/mm/page_alloc.c | 25 +++++++++++++++++-------- 5 files changed, 31 insertions(+), 13 deletions(-)
mm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-enum1 +17 -8
@@ -2062,17 +2062,24 @@ static inline unsigned long wait_table_b* done. Non-atomic initialization, single-pass. */ void __meminit memmap_init_zone (unsigned long size,int nid,unsigned long zone, -unsigned long start_pfn) +unsigned long start_pfn,enum memmap_context context) {struct page *page;unsigned long end_pfn = start_pfn + size;unsigned long pfn;for (pfn = start_pfn; pfn < end_pfn; pfn++) { -if (!early_pfn_valid (pfn)) -continue ; -if (!early_pfn_in_nid (pfn, nid)) -continue ; +/* +* There can be holes in boot-time mem_map[]s +* handed to this function. They do not +* exist on hotplugged memory. +*/ +if (context ==MEMMAP_EARLY ) { +if (!early_pfn_valid (pfn)) +continue ; +if (!early_pfn_in_nid (pfn, nid)) +continue ; + } page =pfn_to_page (pfn);set_page_links (page, zone, nid, pfn);init_page_count (page);
@@ -2102,7 +2109,7 @@ void zone_init_free_lists(struct pglist_#ifndef __HAVE_ARCH_MEMMAP_INIT#define memmap_init (size, nid, zone, start_pfn) \ - memmap_init_zone((size), (nid), (zone), (start_pfn)) + memmap_init_zone((size), (nid), (zone), (start_pfn), MEMMAP_EARLY)#endif static int __cpuinit zone_batchsize (struct zone *zone)
@@ -2348,7 +2355,8 @@ static __meminit void zone_pcp_init(stru__meminit int init_currently_empty_zone (struct zone *zone,unsigned long zone_start_pfn, -unsigned long size) +unsigned long size, +enum memmap_context context) {struct pglist_data *pgdat = zone->zone_pgdat;int ret;
@@ -2792,7 +2800,8 @@ static void __meminit free_area_init_corif (!size)continue ; - ret =init_currently_empty_zone (zone, zone_start_pfn, size); + ret =init_currently_empty_zone (zone, zone_start_pfn, + size,MEMMAP_EARLY );BUG_ON (ret); zone_start_pfn += size; }
include/linux/mm.h renamed from include/linux/mm.h~sparsemem-enum1 +6 -1
@@ -979,7 +979,12 @@ extern int early_pfn_to_nid(unsigned lon#endif /* CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID */ #endif /* CONFIG_ARCH_POPULATES_NODE_MAP */ extern void set_dma_reserve (unsigned long new_dma_reserve); -extern void memmap_init_zone (unsigned long ,int ,unsigned long ,unsigned long ); +enum memmap_context { +MEMMAP_EARLY , +MEMMAP_HOTPLUG , +}; +extern void memmap_init_zone (unsigned long ,int ,unsigned long , +unsigned long ,enum memmap_context );extern void setup_per_zone_pages_min (void );extern void mem_init (void );extern void show_mem (void );
mm/memory_hotplug.c renamed from mm/memory_hotplug.c~sparsemem-enum1 +4 -2
@@ -67,11 +67,13 @@ static int __add_zone(struct zone *zone, zone_type = zone - pgdat->node_zones;if (!populated_zone (zone)) {int ret =0 ; - ret =init_currently_empty_zone (zone, phys_start_pfn, nr_pages); + ret =init_currently_empty_zone (zone, phys_start_pfn, + nr_pages,MEMMAP_HOTPLUG );if (ret <0 )return ret; } -memmap_init_zone (nr_pages, nid, zone_type, phys_start_pfn); +memmap_init_zone (nr_pages, nid, zone_type, + phys_start_pfn,MEMMAP_HOTPLUG );return 0 ; }
arch/s390/mm/vmem.c renamed from arch/s390/mm/vmem.c~sparsemem-enum1 +2 -1
@@ -61,7 +61,8 @@ void memmap_init(unsigned long size, intif (map_start < map_end)memmap_init_zone ((unsigned long )(map_end - map_start), - nid, zone,page_to_pfn (map_start)); + nid, zone,page_to_pfn (map_start), + context); } }
include/linux/mmzone.h renamed from include/linux/mmzone.h~sparsemem-enum1 +2 -1
@@ -474,7 +474,8 @@ int zone_watermark_ok(struct zone *z, in int classzone_idx, int alloc_flags);extern int init_currently_empty_zone (struct zone *zone,unsigned long start_pfn, -unsigned long size); +unsigned long size, +enum memmap_context context);#ifdef CONFIG_HAVE_MEMORY_PRESENT void memory_present (int nid,unsigned long start,unsigned long end);
_
-- Dave
PATCH 1/1 Fix sparsemem on Cell (take 3)
In reply to Arnd BergmannI dropped this on the floor over Christmas. This has had a few smoke tests on ppc64 and i386 and is ready for -mm. Against 2.6.20-rc2-mm1.
The following patch fixes an oops experienced on the Cell architecture when init-time functions, early_*(), are called at runtime. It alters the call paths to make sure that the callers explicitly say whether the call is being made on behalf of a hotplug even, or happening at boot-time.
---
lxc-dave/arch/s390/mm/vmem.c | 3 ++- lxc-dave/include/linux/mm.h | 7 ++++++- lxc-dave/include/linux/mmzone.h | 3 ++- lxc-dave/mm/memory_hotplug.c | 6 ++++-- lxc-dave/mm/page_alloc.c | 25 +++++++++++++++++-------- 5 files changed, 31 insertions(+), 13 deletions(-)
mm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-enum1 +17 -8
@@ -2062,17 +2062,24 @@ static inline unsigned long wait_table_b* done. Non-atomic initialization, single-pass. */ void __meminit memmap_init_zone (unsigned long size,int nid,unsigned long zone, -unsigned long start_pfn) +unsigned long start_pfn,enum memmap_context context) {struct page *page;unsigned long end_pfn = start_pfn + size;unsigned long pfn;for (pfn = start_pfn; pfn < end_pfn; pfn++) { -if (!early_pfn_valid (pfn)) -continue ; -if (!early_pfn_in_nid (pfn, nid)) -continue ; +/* +* There can be holes in boot-time mem_map[]s +* handed to this function. They do not +* exist on hotplugged memory. +*/ +if (context ==MEMMAP_EARLY ) { +if (!early_pfn_valid (pfn)) +continue ; +if (!early_pfn_in_nid (pfn, nid)) +continue ; + } page =pfn_to_page (pfn);set_page_links (page, zone, nid, pfn);init_page_count (page);
@@ -2102,7 +2109,7 @@ void zone_init_free_lists(struct pglist_#ifndef __HAVE_ARCH_MEMMAP_INIT#define memmap_init (size, nid, zone, start_pfn) \ - memmap_init_zone((size), (nid), (zone), (start_pfn)) + memmap_init_zone((size), (nid), (zone), (start_pfn), MEMMAP_EARLY)#endif static int __cpuinit zone_batchsize (struct zone *zone)
@@ -2348,7 +2355,8 @@ static __meminit void zone_pcp_init(stru__meminit int init_currently_empty_zone (struct zone *zone,unsigned long zone_start_pfn, -unsigned long size) +unsigned long size, +enum memmap_context context) {struct pglist_data *pgdat = zone->zone_pgdat;int ret;
@@ -2792,7 +2800,8 @@ static void __meminit free_area_init_corif (!size)continue ; - ret =init_currently_empty_zone (zone, zone_start_pfn, size); + ret =init_currently_empty_zone (zone, zone_start_pfn, + size,MEMMAP_EARLY );BUG_ON (ret); zone_start_pfn += size; }
include/linux/mm.h renamed from include/linux/mm.h~sparsemem-enum1 +6 -1
@@ -979,7 +979,12 @@ extern int early_pfn_to_nid(unsigned lon#endif /* CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID */ #endif /* CONFIG_ARCH_POPULATES_NODE_MAP */ extern void set_dma_reserve (unsigned long new_dma_reserve); -extern void memmap_init_zone (unsigned long ,int ,unsigned long ,unsigned long ); +enum memmap_context { +MEMMAP_EARLY , +MEMMAP_HOTPLUG , +}; +extern void memmap_init_zone (unsigned long ,int ,unsigned long , +unsigned long ,enum memmap_context );extern void setup_per_zone_pages_min (void );extern void mem_init (void );extern void show_mem (void );
mm/memory_hotplug.c renamed from mm/memory_hotplug.c~sparsemem-enum1 +4 -2
@@ -67,11 +67,13 @@ static int __add_zone(struct zone *zone, zone_type = zone - pgdat->node_zones;if (!populated_zone (zone)) {int ret =0 ; - ret =init_currently_empty_zone (zone, phys_start_pfn, nr_pages); + ret =init_currently_empty_zone (zone, phys_start_pfn, + nr_pages,MEMMAP_HOTPLUG );if (ret <0 )return ret; } -memmap_init_zone (nr_pages, nid, zone_type, phys_start_pfn); +memmap_init_zone (nr_pages, nid, zone_type, + phys_start_pfn,MEMMAP_HOTPLUG );return 0 ; }
arch/s390/mm/vmem.c renamed from arch/s390/mm/vmem.c~sparsemem-enum1 +2 -1
@@ -61,7 +61,8 @@ void memmap_init(unsigned long size, intif (map_start < map_end)memmap_init_zone ((unsigned long )(map_end - map_start), - nid, zone,page_to_pfn (map_start)); + nid, zone,page_to_pfn (map_start), + context); } }
include/linux/mmzone.h renamed from include/linux/mmzone.h~sparsemem-enum1 +2 -1
@@ -474,7 +474,8 @@ int zone_watermark_ok(struct zone *z, in int classzone_idx, int alloc_flags);extern int init_currently_empty_zone (struct zone *zone,unsigned long start_pfn, -unsigned long size); +unsigned long size, +enum memmap_context context);#ifdef CONFIG_HAVE_MEMORY_PRESENT void memory_present (int nid,unsigned long start,unsigned long end);
_
-- Dave
Re: [PATCH] Fix sparsemem on Cell (take 3)
Quoted 2 lines
I dropped this on the floor over Christmas. This has had a few smoke tests on ppc64 and i386 and is ready for -mm. Against 2.6.20-rc2-mm1.
Could this break ia64, given that it uses memmap_init_zone()?
Re: [PATCH] Fix sparsemem on Cell (take 3)
Quoted 4 lines · John Rose
Quoted 2 lines
I dropped this on the floor over Christmas. This has had a few smoke tests on ppc64 and i386 and is ready for -mm. Against 2.6.20-rc2-mm1.
Could this break ia64, given that it uses
memmap_init_zone()?
You are right, I think it does.
Here's an updated patch to replace the earlier one. I had to move the enum definition over to a different header because ia64 evidently has a different include order.
---
The following patch fixes an oops experienced on the Cell architecture when init-time functions, early_*(), are called at runtime. It alters the call paths to make sure that the callers explicitly say whether the call is being made on behalf of a hotplug even, or happening at boot-time.
It has been compile tested on ia64, s390, i386 and x86_64.
---
lxc-dave/arch/ia64/mm/init.c | 5 +++-- lxc-dave/arch/s390/mm/vmem.c | 3 ++- lxc-dave/include/linux/mm.h | 3 ++- lxc-dave/include/linux/mmzone.h | 8 ++++++-- lxc-dave/mm/memory_hotplug.c | 6 ++++-- lxc-dave/mm/page_alloc.c | 25 +++++++++++++++++-------- 6 files changed, 34 insertions(+), 16 deletions(-)
arch/s390/mm/vmem.c renamed from arch/s390/mm/vmem.c~Re-_PATCH_Fix_sparsemem_on_Cell +2 -1
@@ -61,7 +61,8 @@ void memmap_init(unsigned long size, intif (map_start < map_end)memmap_init_zone ((unsigned long )(map_end - map_start), - nid, zone,page_to_pfn (map_start)); + nid, zone,page_to_pfn (map_start), +MEMMAP_EARLY ); } }
include/linux/mm.h renamed from include/linux/mm.h~Re-_PATCH_Fix_sparsemem_on_Cell +2 -1
@@ -979,7 +979,8 @@ extern int early_pfn_to_nid(unsigned lon#endif /* CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID */ #endif /* CONFIG_ARCH_POPULATES_NODE_MAP */ extern void set_dma_reserve (unsigned long new_dma_reserve); -extern void memmap_init_zone (unsigned long ,int ,unsigned long ,unsigned long ); +extern void memmap_init_zone (unsigned long ,int ,unsigned long , +unsigned long ,enum memmap_context );extern void setup_per_zone_pages_min (void );extern void mem_init (void );extern void show_mem (void );
include/linux/mmzone.h renamed from include/linux/mmzone.h~Re-_PATCH_Fix_sparsemem_on_Cell +6 -2
@@ -471,9 +471,13 @@ void build_all_zonelists(void);void wakeup_kswapd (struct zone *zone,int order);int zone_watermark_ok (struct zone *z,int order,unsigned long mark,int classzone_idx,int alloc_flags); - +enum memmap_context { +MEMMAP_EARLY , +MEMMAP_HOTPLUG , +};extern int init_currently_empty_zone (struct zone *zone,unsigned long start_pfn, -unsigned long size); +unsigned long size, +enum memmap_context context);#ifdef CONFIG_HAVE_MEMORY_PRESENT void memory_present (int nid,unsigned long start,unsigned long end);
mm/memory_hotplug.c renamed from mm/memory_hotplug.c~Re-_PATCH_Fix_sparsemem_on_Cell +4 -2
@@ -67,11 +67,13 @@ static int __add_zone(struct zone *zone, zone_type = zone - pgdat->node_zones;if (!populated_zone (zone)) {int ret =0 ; - ret =init_currently_empty_zone (zone, phys_start_pfn, nr_pages); + ret =init_currently_empty_zone (zone, phys_start_pfn, + nr_pages,MEMMAP_HOTPLUG );if (ret <0 )return ret; } -memmap_init_zone (nr_pages, nid, zone_type, phys_start_pfn); +memmap_init_zone (nr_pages, nid, zone_type, + phys_start_pfn,MEMMAP_HOTPLUG );return 0 ; }
mm/page_alloc.c renamed from mm/page_alloc.c~Re-_PATCH_Fix_sparsemem_on_Cell +17 -8
@@ -2062,17 +2062,24 @@ static inline unsigned long wait_table_b* done. Non-atomic initialization, single-pass. */ void __meminit memmap_init_zone (unsigned long size,int nid,unsigned long zone, -unsigned long start_pfn) +unsigned long start_pfn,enum memmap_context context) {struct page *page;unsigned long end_pfn = start_pfn + size;unsigned long pfn;for (pfn = start_pfn; pfn < end_pfn; pfn++) { -if (!early_pfn_valid (pfn)) -continue ; -if (!early_pfn_in_nid (pfn, nid)) -continue ; +/* +* There can be holes in boot-time mem_map[]s +* handed to this function. They do not +* exist on hotplugged memory. +*/ +if (context ==MEMMAP_EARLY ) { +if (!early_pfn_valid (pfn)) +continue ; +if (!early_pfn_in_nid (pfn, nid)) +continue ; + } page =pfn_to_page (pfn);set_page_links (page, zone, nid, pfn);init_page_count (page);
@@ -2102,7 +2109,7 @@ void zone_init_free_lists(struct pglist_#ifndef __HAVE_ARCH_MEMMAP_INIT#define memmap_init (size, nid, zone, start_pfn) \ - memmap_init_zone((size), (nid), (zone), (start_pfn)) + memmap_init_zone((size), (nid), (zone), (start_pfn), MEMMAP_EARLY)#endif static int __cpuinit zone_batchsize (struct zone *zone)
@@ -2348,7 +2355,8 @@ static __meminit void zone_pcp_init(stru__meminit int init_currently_empty_zone (struct zone *zone,unsigned long zone_start_pfn, -unsigned long size) +unsigned long size, +enum memmap_context context) {struct pglist_data *pgdat = zone->zone_pgdat;int ret;
@@ -2792,7 +2800,8 @@ static void __meminit free_area_init_corif (!size)continue ; - ret =init_currently_empty_zone (zone, zone_start_pfn, size); + ret =init_currently_empty_zone (zone, zone_start_pfn, + size,MEMMAP_EARLY );BUG_ON (ret); zone_start_pfn += size; }
arch/ia64/mm/init.c renamed from arch/ia64/mm/init.c~Re-_PATCH_Fix_sparsemem_on_Cell +3 -2
@@ -541,7 +541,8 @@ virtual_memmap_init (u64 start, u64 end,if (map_start < map_end)memmap_init_zone ((unsigned long )(map_end - map_start), - args->nid, args->zone,page_to_pfn (map_start)); + args->nid, args->zone,page_to_pfn (map_start), +MEMMAP_EARLY );return 0 ; }
@@ -550,7 +551,7 @@ memmap_init (unsigned long size, int nid unsigned long start_pfn) {if (!vmem_map) -memmap_init_zone (size, nid, zone, start_pfn); +memmap_init_zone (size, nid, zone, start_pfn,MEMMAP_EARLY );else {struct page *start;struct memmap_init_callback_data args;
_
-- Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Arnd Bergmann
Acked-byRe: [PATCH] Fix sparsemem on Cell (take 3)
Quoted 7 lines · Dave Hansen
The following patch fixes an oops experienced on the Cell architecture when init-time functions, early_*(), are called at runtime. It alters the call paths to make sure that the callers explicitly say whether the call is being made on behalf of a hotplug even, or happening at boot-time.
It has been compile tested on ia64, s390, i386 and
x86_64.
I can't test it here, since I'm travelling at the moment, but this version looks good to me. Thanks for picking it up again!
Quoted 1 line
Signed-off-by Dave Hansen <[email protected]>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH] Fix sparsemem on Cell (take 3)
In reply to Dave HansenQuoted 10 lines · Dave Hansen
Quoted 1 line · John Rose
Could this break ia64, given that it uses
memmap_init_zone()?You are right, I think it does.
Here's an updated patch to replace the earlier one. I had to move the enum definition over to a different header because ia64 evidently has a different include order.
Boot tested OK on ia64 with this latest version of the patch.
Tim
_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [PATCH] Fix sparsemem on Cell (take 3)
In reply to Dave HansenQuoted 4 lines · Dave Hansen
Quoted 1 line · John Rose
Could this break ia64, given that it uses
memmap_init_zone()?You are right, I think it does.
Boot tested OK on ia64 with this latest version of the patch.
(forgot to click plain text on gmail the first time..sorry if you got html mail or repeat)
Tim
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 42 lines · Dave Hansen
I think the comments added say it pretty well, but I'll repeat it here.
This fix is pretty similar in concept to the one that Arnd posted as a temporary workaround, but I've added a few comments explaining what the actual assumptions are, and improved it a wee little bit.
The end goal here is to simply avoid calling the early_*() functions when it is _not_ early. Those functions stop working as soon as
free_initmem()is called.system_stateis set toSYSTEM_RUNNINGjust afterfree_initmem()is called, so it seems appropriate to use here.I did think twice about actually using
SYSTEM_RUNNINGbecause we moved away from it in other parts of memory hotplug, but those were actually for _allocations_ in favor ofslab_is_available(), and we really don't care about the slab here.The only other assumption is that all memory-hotplug-time pages given to
memmap_init_zone()are valid and able to be onlined into any any zone after the system is running. The "valid" part is really just a question of whether or not a 'struct page' is there for the pfn, and *not* whether there is actual memory. Since all sparsemem sections have contiguous mem_map[]s within them, and we only memory hotplug entire sparsemem sections, we can be confident that this assumption will hold.As for the memory being in the right node, we'll assume tha memory hotplug is putting things in the right node.
Signed-off-by Dave Hansen <[email protected]>---
lxc-dave/init/main.c | 4 ++++ lxc-dave/mm/page_alloc.c | 28 +++++++++++++++++++++++++--- 2 files changed, 29 insertions(+), 3 deletions(-)diff -puN
init/main.c~sparsemem-fixinit/main.c
init/main.c static int init(void * unused) · line 775
Quoted 6 lines
init/main.c renamed from init/main.c~sparsemem-fix +3
-0@@ -770,6 +770,10 @@ static int init(void * unused)free_initmem ();unlock_kernel ();mark_rodata_ro (); +/* +* Memory hotplug requires that this system_state transition +* happer after free_initmem(). (see memmap_init_zone())
s/happer/happens/
Other than that, can't this possibly race and crash here? I mean, it's not a big race window, but it can happen, no?
Quoted 57 lines
init/main.c renamed from init/main.c~sparsemem-fix +1
-0+*/ system_state =SYSTEM_RUNNING ;numa_default_policy ();diff -puN
mm/page_alloc.c~sparsemem-fixmm/page_alloc.cmm/page_alloc.c renamed from mm/page_alloc.c~sparsemem-fix +25
-3@@ -2056,6 +2056,30 @@ static inline unsigned long wait_table_b#define LONG_ALIGN (x) (((x)+(sizeof(long))-1)&~((sizeof(long))-1)) +static int can_online_pfn_into_nid (unsigned long pfn,int nid) +{ +/* +* There are two things that make this work: +* 1. The early_pfn...() functions are __init and +* use __initdata. If the system is < SYSTEM_RUNNING, +* those functions and their data will still exist. +* 2. We also assume that all actual memory hotplug +* (as opposed to boot-time) calls to this are only +* for contiguous memory regions. With sparsemem, +* this guaranteed is easy because all sections are +* contiguous and we never online more than one +* section at a time. Boot-time memory can have holes +* anywhere. +*/ +if (system_state >=SYSTEM_RUNNING ) +return 1 ; +if (!early_pfn_valid (pfn)) +return 0 ; +if (!early_pfn_in_nid (pfn, nid)) +return 0 ; +return 1 ; +} +/* * Initially all pages are reserved - free ones are freed * up by free_all_bootmem() once the early boot process is @@ -2069,9 +2093,7 @@ void __meminit memmap_init_zone(unsignedunsigned long pfn;for (pfn = start_pfn; pfn < end_pfn; pfn++) { -if (!early_pfn_valid (pfn)) -continue ; -if (!early_pfn_in_nid (pfn, nid)) +if (!can_online_pfn_into_nid (pfn))continue ; page =pfn_to_page (pfn);set_page_links (page, zone, nid, pfn);_
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Signature · 7 lines
Greetings Michael. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 18 lines · Michael Buesch
Quoted 8 lines · Dave Hansen
lxc-dave/init/main.c | 4 ++++ lxc-dave/mm/page_alloc.c | 28 +++++++++++++++++++++++++--- 2 files changed, 29 insertions(+), 3 deletions(-)diff -puN
init/main.c~sparsemem-fixinit/main.cinit/main.c static int init(void * unused) · line 775
Quoted 6 lines
init/main.c renamed from init/main.c~sparsemem-fix +3
-0@@ -770,6 +770,10 @@ static int init(void * unused)free_initmem ();unlock_kernel ();mark_rodata_ro (); +/* +* Memory hotplug requires that this system_state transition +* happer after free_initmem(). (see memmap_init_zone()) s/happer/happens/
Quoted 2 lines
Other than that, can't this possibly race and crash here? I mean, it's not a big race window, but it can happen, no?
That's a good point. Nice eye.
There are three routes in here: boot-time init, an ACPI call, and a write to a sysfs file. Bootmem is taken care of. The write to a sysfs file can't happen yet because userspace isn't up.
The only question would be about ACPI. I _guess_ an ACPI event could come in at any time, and could hit this race window.
One other thought I had was to add an argument to memmap_init_zone() to indicate that the memory being fed to it was contiguous and did not need the validation checks.
Anybody have thoughts on that?
-- Dave
Quoted 11 lines
The only other assumption is that all memory-hotplug-time pages given to
memmap_init_zone()are valid and able to be onlined into any any zone after the system is running. The "valid" part is really just a question of whether or not a 'struct page' is there for the pfn, and *not* whether there is actual memory. Since all sparsemem sections have contiguous mem_map[]s within them, and we only memory hotplug entire sparsemem sections, we can be confident that this assumption will hold.As for the memory being in the right node, we'll assume tha memory hotplug is putting things in the right node.
BTW, just that people know, what we are adding isn't even memory :-) We are calling __add_pages() to create struct page for the SPE local stores and register space as we use them later from a nopage() handler (and no, we can't use no_pfn just yet for various reasons, notably we need to handle races with unmap_mapping_ranges() and thus have the truncate logic in).
Those pages, thus, must never be onlined. Ever. It might make sense to create a way to inform memory hotplug of that fact, but on the other hand, I wouldn't bother as I have a plan to get rid of those __add_pages() completely and work without struct page, maybe in a 2.6.21 timeframe.
Ben.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>