linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Tameen Khan" <tameen@cisco.com>
To: <linuxppc-dev@lists.linuxppc.org>
Subject: Physical Memory map holes in PPC
Date: Thu, 22 Apr 2004 21:26:41 -0700	[thread overview]
Message-ID: <00b001c428eb$2d8ae740$273147ab@amer.cisco.com> (raw)


Hi,

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
PPC.

Am I right ??
Any input will be appreciated

Thanks
Tameen


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2004-04-23  4:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23  4:26 Tameen Khan [this message]
2004-04-23  6:31 ` Physical Memory map holes in PPC Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2004-12-31 20:01 dheeraj kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='00b001c428eb$2d8ae740$273147ab@amer.cisco.com' \
    --to=tameen@cisco.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).