s390/mem_detect: add debugging output

The s390 specific memory detection code does not call memblock_add,
which would generate debug output if memblock=debug is specified on
the kernel command line. Instead it directly calls memblock_add_range,
which doesn't generate any debug output.
To have a chance to debug early memblock related bugs add an s390
specific memblock_dbg call and a (missing) memblock_dump_all call.

Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>

diff --git a/arch/s390/mm/mem_detect.c b/arch/s390/mm/mem_detect.c
index d612cc3eec6a311e77cfa9a9659fe26308c6a7e6..0389d8d243589d929ff8be2eb273240abd7a8bc1 100644 (file)
--- a/arch/s390/mm/mem_detect.c
+++ b/arch/s390/mm/mem_detect.c
@@ -19,6 +19,8 @@
 
 static inline void memblock_physmem_add(phys_addr_t start, phys_addr_t size)
 {
+       memblock_dbg("memblock_physmem_add: [%#016llx-%#016llx]\n",
+                    start, start + size - 1);
        memblock_add_range(&memblock.memory, start, size, 0, 0);
        memblock_add_range(&memblock.physmem, start, size, 0, 0);
 }
@@ -55,4 +57,5 @@ void __init detect_memory_memblock(void)
        memblock_set_bottom_up(false);
        if (!max_physmem_end)
                max_physmem_end = memblock_end_of_DRAM();
+       memblock_dump_all();
 }