From: Sam Ravnborg <sam@ravnborg.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
ebiederm@xmission.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Consolidate vmlinux.lds.S files
Date: Mon, 13 Jan 2003 23:19:43 +0100 [thread overview]
Message-ID: <20030113221942.GB2423@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0301131309240.24477-100000@chaos.physics.uiowa.edu>
On Mon, Jan 13, 2003 at 01:13:28PM -0600, Kai Germaschewski wrote:
> On Mon, 13 Jan 2003, Sam Ravnborg wrote:
>
> > The purpose was to define common stuff in a single place.
> > Ask Rusty Russell if it is fun to add the same section to > 50
> > .lds files.
> >
> > Based on the feedback I will try to come up with a lighter proposal,
> > that does not hurt readability.
> > I still want the common stuff separated away.
>
> I second this, though I also agree that your first cut was hiding away
> stuff more than necessary.
What I posted was to get feedback, not what I had in mind as first step.
I agree to take small steps - but wanted to find out the direction.
> I would suggest an approach like the following, of course showing only a
> first simple step.
But you do not deal with different alingment of the sections.
I have not yet fully understood all the requirements, but wanted to
keep the original ALIGN settings.
In the patch you posted some architectures use ALIGN(4) {cris},
other nothing, but most of them ALIGN(16).
Is it OK to force them all to ALIGN(16) then?
> A series of steps like this should allow for a serious
> reduction in size of arch/*/vmlinux.lds.S already, while being obviously
> correct and allowing archs to do their own special thing if necessary (in
> particular, IA64 seems to differ from all the other archs).
My main objective was that adding new stuff, like __gpl_ksyms could
be done in one place only.
Or .gnu.linkonce.vermagic, or whatever will be used for that.
Thats why I collected so much in INIT_SECTION_CMD(...).
I will come back with something during the week - as time permits.
Sam
next prev parent reply other threads:[~2003-01-13 22:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 22:07 Sam Ravnborg
2003-01-12 23:09 ` Jeff Garzik
2003-01-12 23:36 ` Ingo Oeser
2003-01-13 18:04 ` Sam Ravnborg
2003-01-13 19:10 ` Eric W. Biederman
2003-01-13 22:11 ` Sam Ravnborg
2003-01-13 19:13 ` Kai Germaschewski
2003-01-13 19:37 ` David Mosberger
2003-01-13 20:30 ` Kai Germaschewski
2003-01-13 21:17 ` David Mosberger
2003-01-14 1:54 ` Eric W. Biederman
2003-01-14 2:18 ` PPP problem with >= 2.4.19 JunHyeok Heo
2003-01-14 5:23 ` Steve Lee
2003-01-15 22:42 ` [RFC] Consolidate vmlinux.lds.S files Kai Germaschewski
2003-01-16 0:19 ` Eric W. Biederman
2003-01-13 22:19 ` Sam Ravnborg [this message]
2003-01-13 23:05 ` Kai Germaschewski
2003-01-13 10:19 ` dada1
2003-01-13 18:08 ` Sam Ravnborg
2003-01-13 11:24 ` Eric W. Biederman
2003-01-14 6:27 Mikael Starvik
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=20030113221942.GB2423@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=ebiederm@xmission.com \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®