Physical Memory map holes in PPC
tameen at cisco.com
Fri Apr 23 14:26:41 EST 2004
I am porting Linux kernel Core dumps (LKCD) to PPC platform (440GX).
Need to figure out if there are holes in Pysical memory map for PPC
architecture, and if yes where are they defined.
For example the equivalent funtion for i386 architecture is page_is_ram()
defined in arch/i386/mm/init.c. It uses the e820 memory map, which is
initialized by the setup code in setup.S ( or it is faked to contain 2
regions 0->640K and 1M ->appropriate_end.... So there's at least a memory
hole from 640K -> 1MB)
I have looked through the boot memory allocator code for PPC and I dont find
a similar memory map. They use a phys_avail array for boot memory allocation
which is initialized to a single region from PPC_MEMSTART to total_memory.
>From this it appears that there are no "holes" in physical memory map for
Am I right ??
Any input will be appreciated
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
More information about the Linuxppc-dev