memlayout_global_init() initializes the first memlayout, which is
assumed to match the initial page-flag nid settings.
This is done in start_kernel() as the initdata used to populate the
memlayout is purged from memory early in the boot process (XXX: When?).
Signed-off-by: Cody P Schafer <c...@linux.vnet.ibm.com>
---
init/main.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/init/main.c b/init/main.c
index 63534a1..a1c2094 100644
--- a/init/main.c
+++ b/init/main.c
@@ -72,6 +72,7 @@
#include <linux/ptrace.h>
#include <linux/blkdev.h>
#include <linux/elevator.h>
+#include <linux/memlayout.h>
#include <asm/io.h>
#include <asm/bugs.h>
@@ -618,6 +619,7 @@ asmlinkage void __init start_kernel(void)
security_init();
dbg_late_init();
vfs_caches_init(totalram_pages);
+ memlayout_global_init();
signals_init();
/* rootfs populating might need page-writeback */
page_writeback_init();
--
1.8.2.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
