linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM kexec SMP problem using exynos4210
Date: Wed, 11 Jan 2012 10:06:23 +0000	[thread overview]
Message-ID: <20120111100623.GA27887@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <4F0D49DD.80305@samsung.com>

On Wed, Jan 11, 2012 at 08:35:41AM +0000, Joonyoung Shim wrote:
> Hi,

Hello [adding linux-arm-kernel],

> I have tested kexec to Nuri board using Exynos4210(Dual-core ARM
> Cortex-A9) on the latest mainline kernel but i am facing one problem.
> 
> The kernel enabled SMP, kernel_kexec() calls machine_shutdown to stop
> all cpus except current cpu and jumps to the new kernel but the kernel
> is hanged soon.
> 
> I used cpu_down(1) to make disabled cpu1 instead of smp_send_stop of
> machine_shutdown and it is booted successfully to new kernel.
> 
> Any ideas?

I suspect that the secondary CPUs are not being parked correctly in the first
kernel. For this, you need to implement platform_cpu_kill for your platform.

Given that exynos just does:

int platform_cpu_kill(unsigned int cpu)
{
	return 1;
}

then I'm not surprised it doesn't work. Try adding something in there which puts
the CPU into a state where it can be booted by the next kernel.

I considered adding a purely software mechanism for doing this (in fact, I
prototyped something up on vexpress) but after discussions with some board
maintainers it became clear that most SMP SoCs have hardware assists for
hotplug, and the software approach is really only need for things like the
ARM development boards.

Will

       reply	other threads:[~2012-01-11 10:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F0D49DD.80305@samsung.com>
2012-01-11 10:06 ` Will Deacon [this message]
2012-01-11 10:23   ` ARM kexec SMP problem using exynos4210 Joonyoung Shim
2012-01-11 11:03     ` Will Deacon
2012-01-11 17:20       ` McClintock Matthew-B29882
2012-01-11 17:42         ` Will Deacon
2012-01-11  8:45 Joonyoung Shim

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=20120111100623.GA27887@mudshark.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --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).