From: ebiederm@xmission.com (Eric W. Biederman)
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: linux-tegra@vger.kernel.org, Will Deacon <will.deacon@arm.com>,
kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org,
Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH] kexec: disable non-boot CPUs
Date: Wed, 19 Dec 2012 15:55:36 -0800 [thread overview]
Message-ID: <87mwx9y4uf.fsf@xmission.com> (raw)
In-Reply-To: <1355960681-32015-1-git-send-email-swarren@wwwdotorg.org> (Stephen Warren's message of "Wed, 19 Dec 2012 16:44:41 -0700")
Stephen Warren <swarren@wwwdotorg.org> writes:
> From: Stephen Warren <swarren@nvidia.com>
>
> Both the regular reboot and shutdown paths do this. It seems reasonable
> for kexec to work the same way.
>
> On the Tegra ARM SoC at least, this change allows kexec to work with SMP
> enabled. ARM's machine_shutdown() simply puts all CPUs into a loop. If
> the code of that loop is over-written, the CPUs may crash, and cause the
> kexec'd kernel not to be able to initialize them. In practice, this
> causes the kexec'd kernel to hang and/or crash. The intended way to
> solve this is for ARM machines to provide a cpu_kill SMP operation to
> e.g. power down the CPUs, or place them in reset. However, at least on
> Tegra, the implementation of that function would simply be duplicating
> the hotplug code that already exists, so it seems simpler to just call
> disable_nonboot_cpus() for the kexec path, just like reboot/shutdown.
I would like to ack this but I think this is one of those differences
for which there is a reason.
On x86 this happens in machine_shutdown.
Before this can be merged someone needs to look into the history and
see why we don't share this code path.
My hunch is because it was duplication of effort and the stop machine
code has historically been fragile.
Eric
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
> kernel/kexec.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/kexec.c b/kernel/kexec.c
> index 5e4bd78..6fe74d3 100644
> --- a/kernel/kexec.c
> +++ b/kernel/kexec.c
> @@ -1570,6 +1570,7 @@ int kernel_kexec(void)
> #endif
> {
> kernel_restart_prepare(NULL);
> + disable_nonboot_cpus();
> printk(KERN_EMERG "Starting new kernel\n");
> machine_shutdown();
> }
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-12-19 23:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 23:44 [PATCH] kexec: disable non-boot CPUs Stephen Warren
2012-12-19 23:55 ` Eric W. Biederman [this message]
2012-12-20 10:49 ` Will Deacon
2012-12-20 17:21 ` Stephen Warren
2012-12-20 17:36 ` Will Deacon
2012-12-20 17:59 ` Stephen Warren
2012-12-20 20:15 ` Stephen Warren
2012-12-23 11:06 ` Will Deacon
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=87mwx9y4uf.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=will.deacon@arm.com \
/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