From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: socfpga: add smp_ops.cpu_kill to make kexec/kdump available
Date: Tue, 2 Jun 2015 09:38:04 +0100 [thread overview]
Message-ID: <20150602083804.GX2067@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <XNM1$3$0$0$$3$3$3$A$0000051U556d3fe3@hitachi.com>
On Tue, Jun 02, 2015 at 02:32:19PM +0900, hiraku.toyooka.gu at hitachi.com wrote:
> Before kexec soft reboot, secondary CPU's IRQs except for per-cpu twd are
> migrated from a CPU going offline to CPU0 by migrate_irqs(). The twd is
> stopped by twd_timer_cpu_notify(). As a result, secondary CPU has no
> interrupt source before entering WFI loop.
I wasn't thinking of SPIs and PPIs, but SGIs - the IPI interrupts coming
from the boot CPU.
> After staring kexec'd kernel, all interrupts are sent to CPU0 by default
> and CPU0 resets the secondary CPUs in socfpga_boot_secondary().
> I think it's the reason why kexec in socfpga succeeds.
If you have a way to reset CPU0, why are you not using this for hotplug
when a CPU is hot-unplugged?
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-06-02 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 5:38 [PATCH] ARM: socfpga: add smp_ops.cpu_kill to make kexec/kdump available Hiraku Toyooka
2015-05-29 8:33 ` Russell King - ARM Linux
2015-06-02 5:32 ` hiraku.toyooka.gu at hitachi.com
2015-06-02 8:38 ` Russell King - ARM Linux [this message]
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=20150602083804.GX2067@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).