[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F90DB37.9080702@zytor.com>
Date: Thu, 19 Apr 2012 20:42:47 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
CC: David Daney <david.s.daney@...il.com>,
David Daney <ddaney.cavm@...il.com>,
Ralf Baechle <ralf@...ux-mips.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
Michal Marek <mmarek@...e.cz>, linux-kernel@...r.kernel.org,
linux-mips@...ux-mips.org,
Andrew Morton <akpm@...ux-foundation.org>,
David Daney <david.daney@...ium.com>
Subject: Re: [PATCH v1 1/5] scripts: Add sortextable to sort the kernel's
exception table.
On 04/19/2012 08:31 PM, Linus Torvalds wrote:
> On Thu, Apr 19, 2012 at 8:17 PM, David Daney <david.s.daney@...il.com> wrote:
>>
>> I hadn't considered that the image was relocatable. Our MIPS kernels never
>> have relocations.
>>
>> I am working on a version of this that handles the relocations. It
>> shouldn't be too difficult.
>
> It might be better to just make the rule be that we don't have
> relocations there - make everything relative to the start of the code
> segment or something.
>
> On x86, we already use that _ASM_EXTABLE() macro to hide the
> differences between x86-64 and x86-32. So it should be be somewhat
> easy to make that same macro make it relative to the code start, and
> at the same time also make the exception table perhaps be two 32-bit
> words rather than two pointers.
>
> So it would shrink the exception table and avoid relocations at the
> same time. Win-win. No?
>
I don't think we can get _ASM_EXTABLE() to do that work for us, because
we'd need to subtract symbols from two different sections. We would
need the postprocessing tool to take care this, but guess what, we can
do exactly that (and then, as I mentioned, just zero out the relocation
section.)
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists