From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tameen Khan <tameen@cisco.com>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Physical Memory map holes in PPC
Date: Fri, 23 Apr 2004 16:31:30 +1000 [thread overview]
Message-ID: <1082701889.6442.2.camel@gaston> (raw)
In-Reply-To: <00b001c428eb$2d8ae740$273147ab@amer.cisco.com>
> 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.
Most ppc32 don't, though it's fairly dependant on a given board. ppc64
do have holes, though at this point, it's not simple to get to them, the
data structure representing the physical memory map beeing marked __init...
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-23 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 4:26 Physical Memory map holes in PPC Tameen Khan
2004-04-23 6:31 ` Benjamin Herrenschmidt [this message]
-- 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=1082701889.6442.2.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tameen@cisco.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.