linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Michael Neuling <mikey@neuling.org>,
	paulus@samba.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] do firmware feature fixups after features are initialised
Date: Wed, 11 Jul 2007 21:27:27 +1000	[thread overview]
Message-ID: <1184153248.6059.87.camel@localhost.localdomain> (raw)
In-Reply-To: <3269B7A5-2D77-4C4D-B28D-397CB73E8568@kernel.crashing.org>

On Wed, 2007-07-11 at 13:06 +0200, Segher Boessenkool wrote:
> > There are two possibly solutions I see in the long run:
> >
> >  - We could set the FW features earlier on pseries, though that is  
> > a bit
> > annoying because that means doing it before the device-tree is
> > unflattened.
> >
> >  - We could constraint lmb_alloc to the first segment until the FW  
> > fixup
> > occurs, either within lmb_alloc itself, or fixup the callers such as
> > unflatten_device_tree, to pass an explicit limit.
> 
> c) use a different SLB handler during early boot;
> d) preload some SLB entries at very early boot to cover
>     the first 4GB or so.
> 
> d) sounds nice and simple, but will it work?

Nah, best to limit everything at boot to SLB 0. Thing is, 4G is not
enough, you may have more RAM and have allocations from the top.

Ben.

  reply	other threads:[~2007-07-11 11:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08  4:00 [PATCH] do firmware feature fixups after features are initialised Michael Neuling
2007-07-11 10:28 ` Benjamin Herrenschmidt
2007-07-11 11:06   ` Segher Boessenkool
2007-07-11 11:27     ` Benjamin Herrenschmidt [this message]
2007-07-11 11:41       ` Segher Boessenkool
2007-07-11 11:29   ` Arnd Bergmann
2007-07-11 23:23     ` Michael Neuling
2007-07-12  9:36       ` Arnd Bergmann
2007-07-12 15:15         ` Michael Neuling
2007-07-18 21:56     ` [PATCH] fix future firmware feature fixups function failure Michael Neuling
2007-07-18 22:54       ` Arnd Bergmann
2007-07-19  2:55         ` Michael Neuling

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=1184153248.6059.87.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=paulus@samba.org \
    --cc=segher@kernel.crashing.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).