In load_crashdump_segments(), memmap_p[] is used to contain RANGE_RAM
memory range for booting 2nd kernel. Now adding types of RANGE_ACPI and
RANGE_ACPI_NVS to memmap_p, so later we can pass all the types of memory
range to 2nd kernel. These all types of memory ranges are all stored in
memmap_p for later reference.

Signed-off-by: WANG Chao <[email protected]>
---
 kexec/arch/i386/crashdump-x86.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/kexec/arch/i386/crashdump-x86.c b/kexec/arch/i386/crashdump-x86.c
index 6dd2e65..f97d79a 100644
--- a/kexec/arch/i386/crashdump-x86.c
+++ b/kexec/arch/i386/crashdump-x86.c
@@ -1006,12 +1006,15 @@ int load_crashdump_segments(struct kexec_info *info, 
char* mod_cmdline,
 
        /* Inform second kernel about the presence of ACPI tables. */
        for (i = 0; i < CRASH_MAX_MEMORY_RANGES; i++) {
-               unsigned long start, end;
+               unsigned long start, end, size, type;
                if ( !( mem_range[i].type == RANGE_ACPI
                        || mem_range[i].type == RANGE_ACPI_NVS) )
                        continue;
                start = mem_range[i].start;
                end = mem_range[i].end;
+               type = mem_range[i].type;
+               size = end - start + 1;
+               add_memmap(memmap_p, &nr_memmap, start, size, type);
                cmdline_add_memmap_acpi(mod_cmdline, start, end);
        }
        return 0;
-- 
1.9.0


_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

Reply via email to