linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: versatile: don't mark pen as __INIT
Date: Tue, 18 Jun 2013 16:13:43 +0100	[thread overview]
Message-ID: <20130618151343.GA2718@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1371562002.5375.27.camel@linaro1.home>

On Tue, Jun 18, 2013 at 02:26:42PM +0100, Jon Medhurst (Tixy) wrote:
> On Mon, 2013-06-10 at 16:07 +0100, Mark Rutland wrote:
> > When booting fewer cores than are physically present on a versatile
> > platform (e.g. when passing maxcpus=N on the command line), some
> > secondary cores may remain in the holding pen, which is marked __INIT.
> > Late in the boot process, the memory comprising the holding pen will be
> > released to the kernel for more general use, and may be overwritten with
> > arbitrary data, which can cause the held secondaries to start behaving
> > unpredictably. This can lead to all manner of odd behaviour from the
> > kernel.
> > 
> > Instead don't mark the section as __INIT. This means we can't reuse the
> > pen memory, but we won't get secondaries corrupting the rest of the
> > kernel.
> > 
> > Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> > Acked-by: Pawel Moll <pawel.moll@arm.com>
> > Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> > ---
> 
> This gives section mismatch warnings when compiling with
> vexpress_defconfig:
> 
>         WARNING: vmlinux.o(.text+0x14128): Section mismatch in reference from the variable pen to the function .cpuinit.text:secondary_startup()
>         The function pen() references
>         the function __cpuinit secondary_startup().
>         This is often because pen lacks a __cpuinit 
>         annotation or the annotation of secondary_startup is wrong.
>         
>         WARNING: vmlinux.o(.text+0x14130): Section mismatch in reference from the variable pen to the variable .cpuinit.data:pen_release
>         The function pen() references
>         the variable __cpuinitdata pen_release.
>         This is often because pen lacks a __cpuinitdata 
>         annotation or the annotation of pen_release is wrong.
> 
> wonder if this is opening up a small can of worms...?

With the death of __cpuinit and __CPUINIT, this becomes a non-issue.
Realistically, how many ARM platforms are built without CPU hotplug?
My guess is none what so ever, because CPU hotplug is needed for PM.

  reply	other threads:[~2013-06-18 15:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10 15:07 [PATCH] arm: versatile: don't mark pen as __INIT Mark Rutland
2013-06-10 15:35 ` Jonathan Austin
2013-06-10 18:39 ` Stephen Boyd
2013-06-10 18:52   ` Mark Rutland
2013-06-10 19:09     ` Stephen Boyd
2013-06-10 19:22       ` Stephen Boyd
2013-06-10 20:39         ` Lorenzo Pieralisi
2013-06-10 21:23           ` Stephen Boyd
2013-06-10 23:24 ` Russell King - ARM Linux
2013-06-11  9:04   ` Mark Rutland
2013-06-11 15:43     ` Nicolas Pitre
2013-06-17 10:10       ` Mark Rutland
2013-06-17 11:25         ` Nicolas Pitre
2013-06-20 14:10           ` Mark Rutland
2013-06-18 13:26 ` Jon Medhurst (Tixy)
2013-06-18 15:13   ` Russell King - ARM Linux [this message]
2013-06-18 15:28     ` Jon Medhurst (Tixy)

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=20130618151343.GA2718@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).