Greg Ungerer e87c09a899 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>		2011-12-24 21:47:57 +10:00
..
cache.c
fault.c
hwtest.c
init_mm.c	m68k: print memory layout info in boot log	2011-12-24 21:47:57 +10:00
init_no.c	m68knommu: create common externs for _ram* vars	2011-10-18 14:22:26 +10:00
init.c
kmap.c	m68k: mv kmap_mm.c to kmap.c	2011-05-24 10:03:50 +10:00
Makefile	m68k: merge the mmu and non-mmu mm/Makefile	2011-05-24 10:03:50 +10:00
memory.c
motorola.c	m68k/mm: Set all online nodes in N_NORMAL_MEMORY	2011-04-27 17:36:00 +02:00
sun3kmap.c
sun3mmu.c