Date: Tue, 28 Feb 2006 20:08:43 +0100
From: Sam Ravnborg <sam@ravnborg.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org, akpm@osdl.org, ak@suse.de
Subject: Re: [Patch 2/4] Basic reorder infrastructure
Message-ID: <20060228190843.GA10235@mars.ravnborg.org>
References: <1141053825.2992.125.camel@laptopd505.fenrus.org> <1141054054.2992.130.camel@laptopd505.fenrus.org> <49447.194.237.142.21.1141057876.squirrel@194.237.142.21> <1141060775.2992.149.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1141060775.2992.149.camel@laptopd505.fenrus.org>
User-Agent: Mutt/1.5.11
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1311
Lines: 29

On Mon, Feb 27, 2006 at 06:19:34PM +0100, Arjan van de Ven wrote:
> On Mon, 2006-02-27 at 17:31 +0100, sam@ravnborg.org wrote:
> > > This patch puts the infrastructure in place to allow for a reordering of
> > > functions based inside the vmlinux.
> > 
> > Can we make this general instead of x86_64 only?
> > Then we can use Kconfig to enable it for the architectures where we want it.
> 
> Actually Linus had pretty good arguments to make this per-architecture:
> the list will be different on each architecture.
> 
> (eg my first patch had it more generic; but Linus asked it to be per
> arch, and I agree with the reasons he gave)
The list should be per. architecture for - but I just wanted the rest to
be shared since I assume this will soon be adopted by others.
But on the other hand the rest is very few lines so it is not crucial.

> 
> Also I doubt it can be enabled "blindly" for all architectures; I expect
> more to need hacks similar to the x86_64 entry.S fix before it can
> work...
Which is why utilising Kconfig to enable it would make sense.

	Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/