From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bottomley Subject: Re: [PATCH 1/5] vmlinux.lds.h: Include *(.text.*) in TEXT_TEXT Date: Mon, 14 Jun 2010 18:14:59 -0500 Message-ID: <1276557299.5374.847.camel@mulgrave.site> References: <1276519112-11649-1-git-send-email-matt@console-pimps.org> <87y6ehxvby.fsf@linux-g6p1.site> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: Matt Fleming , linux-arch@vger.kernel.org, Arnd Bergmann , linux-kernel@vger.kernel.org, Sam Ravnborg , Michal Marek , Denys Vlasenko , linux-parisc@vger.kernel.org To: Tim Abbott Return-path: In-Reply-To: List-ID: List-Id: linux-parisc.vger.kernel.org On Mon, 2010-06-14 at 18:21 -0400, Tim Abbott wrote: > On Mon, 14 Jun 2010, Matt Fleming wrote: > > > Do these special kernel sections include things like the parisc > > .text.do_softirq, .text.sys_exit, etc? James raised a good objection to > > the parisc patch of this series. I'm guessing most people saw it already > > but I'll paste it here for reference, > > > > This would destroy all of the named parisc text ordering we do above the > > removed line because now you'd have swept up all the function sections > > before we get to them, won't it? > > > > The ordering is an execution speed up on 32 bit systems because our > > relative jump is so short. > > > > Will you changes handle this OK? > > I think I addressed this in my reply to James just now, but to be super > clear, this -ffunction-sections plan involves renaming .text.do_softirq to > .text..do_softirq (etc.) first. OK, so that doesn't make a lot of sense to me; I suspect because you don't understand what parisc is doing. These aren't names of linux special sections ... they're names of function sections. For efficiency, we take specific hot functions and place them together in the linker script so the jumps between them are small enough to be coded as relative on the 32 bit architecture. It's really just a more efficient way of laying out the binary. James