From: Geoff Levand <geoffrey.levand@am•sony.com>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org, Arnd Bergmann <arnd@arndb•de>,
Jimi Xenidis <jimix@pobox•com>
Subject: Re: CONFIG_PS3_USE_LPAR_ADDR dramically increases boot time
Date: Sat, 23 Jun 2007 11:39:17 -0700 [thread overview]
Message-ID: <467D68D5.6070202@am.sony.com> (raw)
In-Reply-To: <1182216218.26853.305.camel@localhost.localdomain>
Benjamin Herrenschmidt wrote:
> On Mon, 2007-06-18 at 20:13 -0400, Jimi Xenidis wrote:
>> > When CONFIG_PS3_USE_LPAR_ADDR=n a translation in the platform code
>> > sets up the page table to map the region to low addresses
>> (continuous
>> > with the boot mem region), but that translation is not compatible
>> > with the mapping scheme used by the spu regions, which use sparse
>> mem.
>>
>> hmm.. sparse mem is for the linear map.
>
> SPE local store used to have special struct pages for it in order to
> return things from nopage(). It was dodgy and racy. I killed that
> recently, it was causing more problem than it was solving. So it should
> be fine now. I'm now using nopfn() and inserting the PTEs directly from
> the nopfn() hook.
>
> So Geoff, you can remove the option for now or make it n by default.
OK, I'll look into it after I return from OLS.
-Geoff
prev parent reply other threads:[~2007-06-23 18:39 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
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 [this message]
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=467D68D5.6070202@am.sony.com \
--to=geoffrey.levand@am$(echo .)sony.com \
--cc=arnd@arndb$(echo .)de \
--cc=benh@kernel$(echo .)crashing.org \
--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