From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Sort exception table at compile time
Date: Mon, 30 Jul 2012 15:40:37 -0700 [thread overview]
Message-ID: <50170D65.4080205@codeaurora.org> (raw)
In-Reply-To: <20120730221911.GB10335@n2100.arm.linux.org.uk>
On 07/30/12 15:19, Russell King - ARM Linux wrote:
> On Mon, Jul 30, 2012 at 11:51:18PM +0200, Sam Ravnborg wrote:
>> Here you should be able to use the macro EXCEPTION_TABLE from
>> vmlinux.lds.h.
>> I cannot see why the ifdef for not NON-MMU case is needed,
>> but if it is needed the macro is not good...
> Because you can not mention the same input section in two different
> places and end up with predictable output from the linker.
>
> We discard the __ex_table for noMMU, but I think the start/stop
> symbols are still referenced somewhere. Dunno, I don't have much to
> do with noMMU ARM, and the only platform I'd be interested in never
> got merged.
I was thinking, perhaps we can ifdef out the exception fixup sections in
the places where they're added? Then we can just use the EXCEPTION_TABLE
macro from vmlinux.lds.h knowing that there are no __ex_table sections
in the input object files?
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@codeaurora.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
David Daney <david.daney@cavium.com>
Subject: Re: [PATCH] ARM: Sort exception table at compile time
Date: Mon, 30 Jul 2012 15:40:37 -0700 [thread overview]
Message-ID: <50170D65.4080205@codeaurora.org> (raw)
In-Reply-To: <20120730221911.GB10335@n2100.arm.linux.org.uk>
On 07/30/12 15:19, Russell King - ARM Linux wrote:
> On Mon, Jul 30, 2012 at 11:51:18PM +0200, Sam Ravnborg wrote:
>> Here you should be able to use the macro EXCEPTION_TABLE from
>> vmlinux.lds.h.
>> I cannot see why the ifdef for not NON-MMU case is needed,
>> but if it is needed the macro is not good...
> Because you can not mention the same input section in two different
> places and end up with predictable output from the linker.
>
> We discard the __ex_table for noMMU, but I think the start/stop
> symbols are still referenced somewhere. Dunno, I don't have much to
> do with noMMU ARM, and the only platform I'd be interested in never
> got merged.
I was thinking, perhaps we can ifdef out the exception fixup sections in
the places where they're added? Then we can just use the EXCEPTION_TABLE
macro from vmlinux.lds.h knowing that there are no __ex_table sections
in the input object files?
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2012-07-30 22:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 21:30 [PATCH] ARM: Sort exception table at compile time Stephen Boyd
2012-07-30 21:30 ` Stephen Boyd
2012-07-30 21:51 ` Sam Ravnborg
2012-07-30 21:51 ` Sam Ravnborg
2012-07-30 22:19 ` Russell King - ARM Linux
2012-07-30 22:19 ` Russell King - ARM Linux
2012-07-30 22:40 ` Stephen Boyd [this message]
2012-07-30 22:40 ` Stephen Boyd
2012-07-30 21:56 ` Russell King - ARM Linux
2012-07-30 21:56 ` Russell King - ARM Linux
2012-07-30 22:38 ` Stephen Boyd
2012-07-30 22:38 ` Stephen Boyd
2012-07-31 20:01 ` Stephen Boyd
2012-07-31 20:01 ` Stephen Boyd
2012-08-22 18:56 ` [PATCHv2] " Stephen Boyd
2012-08-22 18:56 ` Stephen Boyd
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=50170D65.4080205@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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.