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
Date: Tue, 28 Feb 2006 20:08:43 +0100 [thread overview]
Message-ID: <20060228190843.GA10235@mars.ravnborg.org> (raw)
In-Reply-To: <1141060775.2992.149.camel@laptopd505.fenrus.org>
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
next prev parent reply other threads:[~2006-02-28 19:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 15:23 [Patch 0/4] Reordering of functions, try 2 Arjan van de Ven
2006-02-27 15:27 ` [Patch 2/4] Basic reorder infrastructure Arjan van de Ven
2006-02-27 15:41 ` Andi Kleen
2006-02-27 16:31 ` sam
2006-02-27 17:19 ` Arjan van de Ven
2006-02-28 19:08 ` Sam Ravnborg [this message]
2006-03-10 9:45 ` [Patch 2/4] Basic reorder infrastructure - makes linking very slow Andi Kleen
2006-02-27 15:31 ` [Patch 4/4] Tell GCC 4.1 to move unlikely() code to a separate section Arjan van de Ven
2006-02-27 15:39 ` Andi Kleen
2006-02-27 23:33 ` Bill Davidsen
2006-02-27 15:31 ` [Patch 3/4] Move the base kernel to 2Mb to align with TLB boundaries Arjan van de Ven
2006-02-27 15:36 ` Andi Kleen
2006-02-27 15:52 ` Arjan van de Ven
2006-02-27 15:31 ` [Patch 1/4] avoid entry.S functions from reordering Arjan van de Ven
2006-02-27 15:36 ` [Patch 0/4] Reordering of functions, try 2 Andi Kleen
2006-02-27 15:43 ` Arjan van de Ven
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=20060228190843.GA10235@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.