From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: Fix memblock_reserve() to include stext
Date: Wed, 31 Jul 2013 09:43:53 +0000 [thread overview]
Message-ID: <20130731094352.GV24642@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130731055807.14054.70106.sendpatchset@w520>
On Wed, Jul 31, 2013 at 02:58:07PM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@opensource.se>
>
> This fix for the ARM architecture will include stext
> in the memblock_reserve() call to make sure that the
> following symbols are not overwritten (from System.map):
>
> c0008000 T _text
> c0008000 T stext
> ...
> c0008138 T secondary_startup
> ...
> c0009000 T _stext
>
> With this patch applied CPU Hotplug starts working
> again. Without this patch code in secondary_startup
> never gets reached as expected.
>
> This issue started triggering on kernels later than
> v3.10 - perhaps a side effect of the CPU Hotplug init
> section rework - so this is a fix for v3.11-rc.
This is not the right fix. The commit you previously pointed out (removal
of CPU hotplug) probably means there's a missing annotation somewhere in
the code.
And yes - the __CPUINIT just before ENTRY(secondary_startup) was removed
rather than being replaced with a .text (in both head.S and head-nommu.S).
Same goes for ENTRY(lookup_processor_type) in head-common.S. All these
need to be replaced with .text to stop them falling into the head section.
next prev parent reply other threads:[~2013-07-31 9:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 5:58 [PATCH] ARM: Fix memblock_reserve() to include stext Magnus Damm
2013-07-31 9:43 ` Russell King - ARM Linux [this message]
2013-07-31 19:34 ` Magnus Damm
2013-07-31 19:39 ` Russell King - ARM Linux
2013-08-01 7:34 ` Simon Horman
2013-08-01 12:58 ` Paul Gortmaker
2013-08-02 1:32 ` Simon Horman
2013-08-02 3:24 ` Magnus Damm
2013-08-02 9:26 ` Russell King - ARM Linux
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=20130731094352.GV24642@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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 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).