From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 62F6FDDF11 for ; Tue, 19 Jun 2007 11:23:50 +1000 (EST) Subject: Re: CONFIG_PS3_USE_LPAR_ADDR dramically increases boot time From: Benjamin Herrenschmidt To: Jimi Xenidis In-Reply-To: <7F58A02C-5C4C-4717-8D32-65C75C342ADB@pobox.com> References: <200706182314.26918.arnd@arndb.de> <46771140.5000205@am.sony.com> <7F58A02C-5C4C-4717-8D32-65C75C342ADB@pobox.com> Content-Type: text/plain Date: Tue, 19 Jun 2007 11:23:38 +1000 Message-Id: <1182216218.26853.305.camel@localhost.localdomain> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org, Arnd Bergmann List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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. Ben.