mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Hiraku Toyooka <hiraku.toyooka.gu@hitachi.com>
Cc: dinguyen@opensource.altera.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: socfpga: add smp_ops.cpu_kill to make kexec/kdump available
Date: Fri, 29 May 2015 09:33:39 +0100	[thread overview]
Message-ID: <20150529083339.GG2067@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20150529053844.31162.43927.stgit@arietta>

On Fri, May 29, 2015 at 02:38:44PM +0900, Hiraku Toyooka wrote:
> Kexec_load syscall in ARM checks that machine-specific code
> has the smp_ops.cpu_kill() before loading kernel image.
> This patch adds the cpu_kill(), as a result, kexec reboot and
> kernel crash dump become available in mach-socfpga.

Please look at the kexec'd kernel's boot messages.  You will probably
notice that the kexec'd kernel is unable to start the secondary CPUs,
and probably causes them to crash.

As socfpga does not appear to be able to do anything with the secondary
CPUs other than park them in a WFI loop in the _existing_ kernel, when
that existing kernel gets overwritten by the kexec kernel and an interrupt
sent to the CPU, that secondary CPU could very well start executing code
it's not meant to.

So no, this is a bad idea.

Unless secondary CPUs can actually be taken offline, features like kexec
can't be supported on the platform.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2015-05-29  8:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29  5:38 Hiraku Toyooka
2015-05-29  8:33 ` Russell King - ARM Linux [this message]
     [not found]   ` <XNM1$3$0$0$$3$3$3$A$0000051U556d3fe3@hitachi.com>
2015-06-02  8:38     ` Russell King - ARM Linux
2015-06-02 23:40       ` Hiraku Toyooka
2015-06-02 23:52         ` 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=20150529083339.GG2067@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=dinguyen@opensource.altera.com \
    --cc=hiraku.toyooka.gu@hitachi.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®