public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb•de>
To: linuxppc-dev@ozlabs•org
Cc: Jimi Xenidis <jimix@pobox•com>
Subject: Re: CONFIG_PS3_USE_LPAR_ADDR dramically increases boot time
Date: Mon, 18 Jun 2007 23:14:26 +0200	[thread overview]
Message-ID: <200706182314.26918.arnd@arndb.de> (raw)
In-Reply-To: <F4482BED-242B-42AD-96FF-3CB14B6BC5BE@watson.ibm.com>

On Monday 18 June 2007, Jimi Xenidis wrote:
>=20
> The following change set:
> =A0 =A0http://git.kernel.org/?p=3Dlinux/kernel/git/paulus/=20
> powerpc.git;a=3Dcommit;h=3D261efc3f178c8c5b55d76208aee1f39ce247f723
>=20
> setting CONFIG_PS3_USE_LPAR_ADDR (which is the default for PS3) =A0
> changes increases MAX_PHYSADDR_BITS =A0from 44 to 47 which makes the =A0
> array 8 time bigger and takes way longer for sparse_init() to run on =A0
> simulator.
>=20
> Is this really the right approach?
> Cell is actually 42 so could not the special address space be 43 or 44?

Unfortunately, the hypervisor chooses the addresses where things get
mapped, and since they are guest-real, there is no hard limit where
the hypervisor puts them, like the 42 bit limit on bare metal.

I guess this will improve if we get virt_mem_map support on powerpc,
but I'm not sure if that's currently being worked on.

	Arnd <><

  reply	other threads:[~2007-06-18 21:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18 19:45 CONFIG_PS3_USE_LPAR_ADDR dramically increases boot time Jimi Xenidis
2007-06-18 21:14 ` Arnd Bergmann [this message]
2007-06-18 21:27   ` Jimi Xenidis
2007-06-18 23:12     ` Geoff Levand
2007-06-18 23:53       ` Arnd Bergmann
2007-06-18 23:55         ` Geoff Levand
2007-06-19  0:13       ` Jimi Xenidis
2007-06-19  1:23         ` Benjamin Herrenschmidt
2007-06-23 18:39           ` Geoff Levand

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=200706182314.26918.arnd@arndb.de \
    --to=arnd@arndb$(echo .)de \
    --cc=jimix@pobox$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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