aboutsummaryrefslogtreecommitdiffstats
path: root/arch/unicore32/Kconfig.debug
diff options
context:
space:
mode:
authorGreg Ungerer <gerg@uclinux.org>2011-10-13 02:59:55 -0400
committerGreg Ungerer <gerg@uclinux.org>2011-12-24 06:47:57 -0500
commite87c09a899d38d1b6858e010c22a1200fb77965d (patch)
tree4d6fb0c19423589d218e0d9e7161e2758608b5f2 /arch/unicore32/Kconfig.debug
parent361a541dc2373e57cfa7a63e95fbe448ff5675d4 (diff)
m68k: print memory layout info in boot log
Output a table of the kernel memory regions at boot time. This is taken directly from the ARM architecture code that does this. The table looks like this: Virtual kernel memory layout: vector : 0x00000000 - 0x00000400 ( 0 KiB) kmap : 0xd0000000 - 0xe0000000 ( 256 MiB) vmalloc : 0xc0000000 - 0xcfffffff ( 255 MiB) lowmem : 0x00000000 - 0x02000000 ( 32 MiB) .init : 0x00128000 - 0x00134000 ( 48 KiB) .text : 0x00020000 - 0x00118d54 ( 996 KiB) .data : 0x00118d60 - 0x00126000 ( 53 KiB) .bss : 0x00134000 - 0x001413e0 ( 53 KiB) This has been very useful while debugging the ColdFire virtual memory support code. But in general I think it is nice to know extacly where the kernel has layed everything out on boot. Signed-off-by: Greg Ungerer <gerg@uclinux.org>
Diffstat (limited to 'arch/unicore32/Kconfig.debug')
0 files changed, 0 insertions, 0 deletions