[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130705213214.GK24642@n2100.arm.linux.org.uk>
Date: Fri, 5 Jul 2013 22:32:15 +0100
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Stephen Warren <swarren@...dotorg.org>
Cc: Paul Gortmaker <paul.gortmaker@...driver.com>,
Will Deacon <will.deacon@....com>,
Joseph Lo <josephl@...dia.com>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-tegra@...r.kernel.org,
Stephen Warren <swarren@...dia.com>
Subject: Re: [PATCH V3] ARM: add missing linker section markup to
head-common.S
On Fri, Jul 05, 2013 at 12:10:55PM -0600, Stephen Warren wrote:
> From: Stephen Warren <swarren@...dia.com>
>
> Macro __INIT is used to place various code in head-common.S into the init
> section. This should be matched by a closing __FINIT. Also, add an
> explicit ".text" to ensure subsequent code is placed into the correct
> section; __FINIT is simply a closing marker to match __INIT and doesn't
> guarantee to revert to .text.
>
> This historically caused no problem, because macro __CPUINIT was used at
> the exact location where __FINIT was missing, which then placed following
> code into the cpuinit section. However, with commit 22f0a2736 "init.h:
> remove __cpuinit sections from the kernel" applied, __CPUINIT becomes a
> no-op, thus leaving all this code in the init section, rather than the
> regular text section. This caused issues such as secondary CPU boot
> failures or crashes.
>
> Signed-off-by: Stephen Warren <swarren@...dia.com>
> Acked-by: Paul Gortmaker <paul.gortmaker@...driver.com>
> ---
> v3: Added .text after __FINIT to force the correct section.
> v2: Moved __FINIT after lookup_processor_type, to correctly match the
> location of __CPUINIT.
Much better, thanks. Please put it in the patch system and I'll send it
along, thanks.
--
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