From: Michal Simek <monstr@monstr.eu>
To: microblaze-uclinux@itee.uq.edu.au
Cc: "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Michal Simek <monstr@monstr.eu>, Sam Ravnborg <sam@ravnborg.org>,
Paul Mundt <lethal@linux-sh.org>, Tony Luck <tony.luck@intel.com>,
John Williams <john.williams@petalogix.com>
Subject: Re: [microblaze-uclinux] [RFC PATCH] linker script: unify usage of discard definition
Date: Mon, 06 Jul 2009 08:17:44 +0200 [thread overview]
Message-ID: <4A519708.80608@monstr.eu> (raw)
In-Reply-To: <4A4E9638.20304@kernel.org>
Tejun Heo wrote:
> Discarded sections in different archs share some commonality but have
> considerable differences. This led to linker script for each arch
> implementing its own /DISCARD/ definition, which makes maintaining
> tedious and adding new entries error-prone.
>
> This patch makes all linker scripts to move discard definitions to the
> end of the linker script and use the common DISCARDS macro. As ld
> uses the first matching section definition, archs can include default
> discarded sections by including them earlier in the linker script.
>
> On x86-64 which explicitly includes EXIT_TEXT, this produces identical
> output as before and all but one archs included directives (include or
> discard) for all default discarded sections, so this patch shouldn't
> cause any behavior difference.
>
> The only problem case is microblaze, which didn't explicitly included
> EXIT_TEXT and DATA but didn't discard them either leaving ld to create
> identically names output sections for them. This patch will make the
> end result different by throwing away exit text and data. It looks
> like the ommission was accidental and throwing away is the right thing
> to do, but I won't push it till someone who knows microblaze confirms
> it.
Please include EXIT_TEXT to .text section. EXIT_DATA can be discard. Patch is below.
Tested-by: Michal Simek <monstr@monstr.eu>
Thanks,
Michal
diff --git a/arch/microblaze/kernel/vmlinux.lds.S b/arch/microblaze/kernel/vmlinux.lds.S
index aa5b0e9..39c0d0b 100644
--- a/arch/microblaze/kernel/vmlinux.lds.S
+++ b/arch/microblaze/kernel/vmlinux.lds.S
@@ -23,8 +23,8 @@ SECTIONS {
_stext = . ;
*(.text .text.*)
*(.fixup)
-
- *(.exitcall.exit)
+ EXIT_TEXT
+ EXIT_CALL
SCHED_TEXT
LOCK_TEXT
KPROBES_TEXT
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
prev parent reply other threads:[~2009-07-06 6:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 23:37 [RFC PATCH] linker script: unify usage of discard definition Tejun Heo
2009-07-03 23:37 ` Tejun Heo
2009-07-04 1:34 ` linux-next submission requirements (Was: [RFC PATCH] linker script: unify usage of discard definition) Stephen Rothwell
2009-07-04 3:18 ` Tejun Heo
2009-07-04 4:03 ` Stephen Rothwell
2009-07-04 4:03 ` Stephen Rothwell
2009-07-04 4:07 ` Tejun Heo
2009-07-04 5:51 ` [RFC PATCH] linker script: unify usage of discard definition Mike Frysinger
2009-07-04 15:37 ` Paul Mundt
2009-07-04 18:40 ` [microblaze-uclinux] " Michal Simek
2009-07-06 6:17 ` Michal Simek [this message]
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=4A519708.80608@monstr.eu \
--to=monstr@monstr.eu \
--cc=john.williams@petalogix.com \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=sam@ravnborg.org \
--cc=tony.luck@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).