Commit a2ce2a95 authored Dec 27, 2016 by Heiko Carstens Committed by Martin Schwidefsky Jan 16, 2017

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>

parent 7be5e359

arch/s390/mm/mem_detect.c

+3 −0

Original line number	Diff line number	Diff line
		@@ -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();
		}

Admin message