[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130702175257.GC21817@windriver.com>
Date: Tue, 2 Jul 2013 13:53:00 -0400
From: Paul Gortmaker <paul.gortmaker@...driver.com>
To: Russell King - ARM Linux <linux@....linux.org.uk>
CC: Joseph Lo <josephl@...dia.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Will Deacon <will.deacon@....com>,
<linux-tegra@...r.kernel.org>
Subject: Re: [PATCH 07/32] arm: delete __cpuinit/__CPUINIT usage from all ARM
users
[Re: [PATCH 07/32] arm: delete __cpuinit/__CPUINIT usage from all ARM users] On 02/07/2013 (Tue 09:58) Russell King - ARM Linux wrote:
> On Tue, Jul 02, 2013 at 04:52:00PM +0800, Joseph Lo wrote:
> > I just tested this series on Tegra platform. It looks broken CPU hotplug
> > function for Tegra at least. The CPU can't plug-in after unplugging. And
> > the system resume function also not working when "enable_nonboot_cpus".
> >
> > Both of the issue cause system hang up. Are we missing something for
> > __cpuinit removal work?
>
> Check that any assembly code you're using where the __CPUINIT* marker has
> been removed is not preceded by an __INIT or similar. This code needs
> to end up in the normal .text, .data or .bss sections now.
Yes, As Russell says it is entirely possible that the earlier section
was __INIT and there was already a missing __FINIT (or .previous).
Hence what was __cpuinit got grandfathered into __INIT instead of
.text/.data/.bss
I'm offline at the moment but will double check myself later this
evening if nothing obvious has been found by then.
Thanks,
Paul.
--
--
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