From: Stephen Warren <swarren@wwwdotorg.org>
To: Will Deacon <will.deacon@arm.com>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
Stephen Warren <swarren@nvidia.com>,
Eric Biederman <ebiederm@xmission.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] kexec: disable non-boot CPUs
Date: Thu, 20 Dec 2012 10:21:56 -0700 [thread overview]
Message-ID: <50D34934.9070106@wwwdotorg.org> (raw)
In-Reply-To: <20121220104945.GC16887@mudshark.cambridge.arm.com>
On 12/20/2012 03:49 AM, Will Deacon wrote:
> Hi Stephen,
>
> On Wed, Dec 19, 2012 at 11:44:41PM +0000, Stephen Warren wrote:
>> 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.
>
> If you do manage to get this merged, please can you follow up with a patch
> to remove the smp_kill_cpus bits from arch/arm/kernel/smp.c please? It only
> exists as a hook to do exactly this and currently nobody is using it afaict.
I originally implemented this in
arch/arm/kernel/process.c:machine_shutdown(), which currently is:
void machine_shutdown(void)
{
#ifdef CONFIG_SMP
smp_send_stop();
#endif
}
and I changed it to something like:
void machine_shutdown(void)
{
#ifdef CONFIG_HOTPLUG_CPU
disable_nonboot_cpus();
#elifdef CONFIG_SMP
smp_send_stop();
#endif
}
... but then figured that moving it up into the core kexec code would be
better, so that everything always worked the same way.
Anyway, the change above addresses Eric's concern about isolating the
change to ARM. Does that seem like a reasonable thing for the ARM code
to do?
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-12-20 17:21 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
2012-12-20 10:49 ` Will Deacon
2012-12-20 17:21 ` Stephen Warren [this message]
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=50D34934.9070106@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=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=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