From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 21 Feb 2007 11:16:53 +1100 From: David Gibson To: Segher Boessenkool Subject: Re: [RFC 3/3] zImage: Exception vector support Message-ID: <20070221001653.GB10231@localhost.localdomain> References: <45D7A914.4040000@am.sony.com> <20070220022538.GH17818@localhost.localdomain> <45DB0448.9080301@am.sony.com> <45DB1759.2010302@am.sony.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Feb 20, 2007 at 05:02:11PM +0100, Segher Boessenkool wrote: > > +ps3) > > + platformo="$object/head.o $object/ps3-hvcall.o $object/ps3.o" > > + ;; > > > > Having those vectors makes a 4MB dead gap in the binary image. The > > ps3's > > loader supports a gziped image so there is no problem, but for the > > general > > case of binary images, there is no way we can have those always in > > there. > > If this is an ELF file, you can put the exception vectors in a > separate segment. Or if you don't need the entry point to > be in the low region, (and you don't need that unless your > boot loader ignores the entry point in the ELF header), you can > copy the vectors in at startup and have no code linked at 0 at > all. No, the initial loader has a hard-wired entry point, that's why this is necessary. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson