diff options
| author | Heiko Carstens <[email protected]> | 2016-12-27 15:14:26 +0100 |
|---|---|---|
| committer | Martin Schwidefsky <[email protected]> | 2017-01-16 07:27:53 +0100 |
| commit | a2ce2a956814b52c062d17422ebbf87ce4f0158d (patch) | |
| tree | e16b07f74de3fc2b9f110aeaee27ec83302051c9 /scripts/gdb/linux/modules.py | |
| parent | 7be5e359a7eaea6ebe761044f6994163f0dd8585 (diff) | |
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 <[email protected]>
Signed-off-by: Martin Schwidefsky <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/modules.py')
0 files changed, 0 insertions, 0 deletions