linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: set_phys_avail() futures question
Date: Thu, 30 Jun 2005 15:06:08 +1000	[thread overview]
Message-ID: <1120107968.31924.42.camel@gaston> (raw)
In-Reply-To: <3FD36254-F985-4040-A68A-72EEB212D8A3@freescale.com>

On Thu, 2005-06-30 at 00:06 -0500, Kumar Gala wrote:
> On Jun 29, 2005, at 6:56 PM, Benjamin Herrenschmidt wrote:
> 
> > 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.
> 
> What this implies to me is that what a flattened OF tree we will no  
> longer need to call set_phys_avail().

It will have to do some equivalent to transfer the reserve map to
mem_pieces tho ...

Ben.

  reply	other threads:[~2005-06-30  5:11 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
2005-06-30  5:06   ` Kumar Gala
2005-06-30  5:06     ` Benjamin Herrenschmidt [this message]
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=1120107968.31924.42.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=kumar.gala@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).