Parsing numa info has been separated to two functions now.

early_initmem_info() only parse info in numa_meminfo and
nodes_parsed. still keep numaq, acpi_numa, amd_numa, dummy
fall back sequence working.

SLIT and numa emulation handling are still left in initmem_init().

Call early_initmem_init before init_mem_mapping() to prepare
to use numa_info with it.

Signed-off-by: Yinghai Lu <ying...@kernel.org>
Cc: Pekka Enberg <penb...@kernel.org>
Cc: Jacob Shin <jacob.s...@amd.com>
---
 arch/x86/kernel/setup.c |   24 ++++++++++--------------
 1 file changed, 10 insertions(+), 14 deletions(-)

diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index 626bc9f..86e1ec0 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -1098,13 +1098,21 @@ void __init setup_arch(char **cmdline_p)
        trim_platform_memory_ranges();
        trim_low_memory_range();
 
+       /*
+        * Parse the ACPI tables for possible boot-time SMP configuration.
+        */
+       acpi_initrd_override_copy();
+       acpi_boot_table_init();
+       early_acpi_boot_init();
+       early_initmem_init();
        init_mem_mapping();
-
+       memblock.current_limit = get_max_mapped();
        early_trap_pf_init();
 
+       reserve_initrd();
+
        setup_real_mode();
 
-       memblock.current_limit = get_max_mapped();
        dma_contiguous_reserve(0);
 
        /*
@@ -1118,24 +1126,12 @@ void __init setup_arch(char **cmdline_p)
        /* Allocate bigger log buffer */
        setup_log_buf(1);
 
-       reserve_initrd();
-
-       acpi_initrd_override_copy();
-
        reserve_crashkernel();
 
        vsmp_init();
 
        io_delay_init();
 
-       /*
-        * Parse the ACPI tables for possible boot-time SMP configuration.
-        */
-       acpi_boot_table_init();
-
-       early_acpi_boot_init();
-
-       early_initmem_init();
        initmem_init();
        memblock_find_dma_reserve();
 
-- 
1.7.10.4

--
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/

Reply via email to