[PATCH] x86: move saving e820_saved to setup_memory_map

From: Yinghai Lu
Date: Thu Jul 03 2008 - 14:38:20 EST



so other path that will override memory_setup or machine_specific_memory_setup could
have e820_saved too

Signed-off-by: Yinghai Lu <yhlu.kernel@xxxxxxxxx>

---
arch/x86/kernel/e820.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)

Index: linux-2.6/arch/x86/kernel/e820.c
===================================================================
--- linux-2.6.orig/arch/x86/kernel/e820.c
+++ linux-2.6/arch/x86/kernel/e820.c
@@ -1294,8 +1294,6 @@ char *__init default_machine_specific_me
e820_add_region(HIGH_MEMORY, mem_size << 10, E820_RAM);
}

- memcpy(&e820_saved, &e820, sizeof(struct e820map));
-
/* In case someone cares... */
return who;
}
@@ -1313,8 +1311,12 @@ char * __init __attribute__((weak)) memo

void __init setup_memory_map(void)
{
+ char *who;
+
+ who = memory_setup();
+ memcpy(&e820_saved, &e820, sizeof(struct e820map));
printk(KERN_INFO "BIOS-provided physical RAM map:\n");
- e820_print_map(memory_setup());
+ e820_print_map(who);
}

#ifdef CONFIG_X86_64
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/