From: Jon Loeliger <jdl@freescale.com>
To: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: set_phys_avail() futures question
Date: Wed, 29 Jun 2005 16:14:28 -0500 [thread overview]
Message-ID: <1120079668.1798.98.camel@cashmere.sps.mot.com> (raw)
Ben (primarily),
I'd like to get your opinion on what the future of
arch/ppc/mm/init.c/set_phys_avail() looks like.
Currently, its job is to traverse the mem_pieces data
and remove a whole series of #ifdef'ed regions of
memory based on configuration options. These regions
are the initrd, the RTAS data, and the AGP special page.
Do you see these regions as being explicitly listed in
the proposed "reserved memory blocks" area of the Flat
Dev Tree header structure?
If so, then they would follow the same conceptual flow
as the ppc64 reservations in the LMB. They would then
be SetPagReserved() and removed from the do_init_bootmem()
regions of memory as well.
Thanks,
jdl
next reply other threads:[~2005-06-29 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 21:14 Jon Loeliger [this message]
2005-06-29 23:56 ` set_phys_avail() futures question Benjamin Herrenschmidt
2005-06-30 5:06 ` Kumar Gala
2005-06-30 5:06 ` Benjamin Herrenschmidt
2005-06-30 5:26 ` Kumar Gala
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=1120079668.1798.98.camel@cashmere.sps.mot.com \
--to=jdl@freescale.com \
--cc=linuxppc-dev@ozlabs.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).