linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Loeliger <jdl@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: set_phys_avail() futures question
Date: Thu, 30 Jun 2005 09:56:51 +1000	[thread overview]
Message-ID: <1120089411.31924.36.camel@gaston> (raw)
In-Reply-To: <1120079668.1798.98.camel@cashmere.sps.mot.com>

On Wed, 2005-06-29 at 16:14 -0500, Jon Loeliger wrote:
> 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?

Yes. initrd for sure, RTAS too, AGP special page well ... I have to
check if we still use that one at all... but it's not allocated in
prom_init so it may need it's own little bit here still.

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

I'm not sure we actually need to explicitely call SetPageReserved(), do
we ? As long as they are not returned to the free pool ...  Oh well,
that can't hurt :)

Ben.

  reply	other threads:[~2005-06-30  0:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 21:14 set_phys_avail() futures question Jon Loeliger
2005-06-29 23:56 ` Benjamin Herrenschmidt [this message]
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=1120089411.31924.36.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=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).