From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: decouple CPU offlining from reboot/shutdown
Date: Tue, 11 Jun 2013 12:08:40 -0600 [thread overview]
Message-ID: <51B767A8.7000506@wwwdotorg.org> (raw)
In-Reply-To: <20130611172342.GJ3439@mudshark.cambridge.arm.com>
On 06/11/2013 11:23 AM, Will Deacon wrote:
> Hi Stephen,
>
> On Mon, Jun 10, 2013 at 07:12:41PM +0100, Stephen Warren wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> machine_shutdown() is a hook for kexec. Add a comment saying so, since
>> it isn't obvious from the function name.
>
> I'd go as far as saying that some of this commit log could be included in
> the comment too, since this comes up time and time again and it's never
> clear!
OK, I'll add some expanded comments to each of the functions.
>> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
>> index 42d6ea2..d7b3d2e 100644
>> --- a/arch/arm/Kconfig
>> +++ b/arch/arm/Kconfig
>> @@ -2028,7 +2028,7 @@ config XIP_PHYS_ADDR
>>
>> config KEXEC
>> bool "Kexec system call (EXPERIMENTAL)"
>> - depends on (!SMP || HOTPLUG_CPU)
>> + depends on (!SMP || (HOTPLUG_CPU && PM_SLEEP_SMP))
>
> PM_SLEEP_SMP selects HOTPLUG_CPU.
Ah, that makes more sense; it explains how code under /just/ #ifdef
PM_SLEEP_SMP can interact with hotplug-related code.
I guess I just checked HOTPLUG for a select/depends and not the other
way around.
>> diff --git a/arch/arm/kernel/process.c b/arch/arm/kernel/process.c
>> @@ -97,13 +97,14 @@ void soft_restart(unsigned long addr)
>> {
>> u64 *stack = soft_restart_stack + ARRAY_SIZE(soft_restart_stack);
>>
>> + BUG_ON(num_online_cpus() > 1);
>
> I think this is overkill, and we could actually scream and try to return an
> error here (we've not yet switched stack, and the upper layers of kexec look
> like they can do something with an error code).
Hmmm. The function returns void, although I suppose I could look into
changing that too?
>> +/* For kexec */
>> void machine_shutdown(void)
>> {
>> -#ifdef CONFIG_SMP
>> - smp_send_stop();
>> +#ifdef CONFIG_PM_SLEEP_SMP
>> + disable_nonboot_cpus();
>> #endif
>
> You can lose the #ifdef here.
The implementation of disable_nonboot_cpus() is #ifdef
CONFIG_PM_SLEEP_SMP, so I think I need that to avoid build errors.
>> + BUG_ON(num_online_cpus() > 1);
>
> Maybe redefine machine_shutdown if !kexec and lose this BUG?
IIUC, machine_shutdown() is only used for kexec now, so I don't think an
alternative implementation is required in the !kexec case?
>> void machine_halt(void)
>> {
>> - machine_shutdown();
>> +#ifdef CONFIG_SMP
>> + smp_send_stop();
>> +#endif
>
> Don't need the #ifdef.
Oh right; I hadn't noticed the inline in smp.h.
next prev parent reply other threads:[~2013-06-11 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 18:12 [PATCH] ARM: decouple CPU offlining from reboot/shutdown Stephen Warren
2013-06-11 17:23 ` Will Deacon
2013-06-11 18:08 ` Stephen Warren [this message]
2013-06-11 18:29 ` Will Deacon
2013-06-11 18:38 ` Stephen Warren
2013-06-12 16:58 ` Will Deacon
2013-06-12 18:09 ` Russell King - ARM Linux
2013-06-12 18:15 ` Stephen Warren
2013-06-11 18:41 ` Stephen Warren
2013-06-12 17:01 ` Will Deacon
2013-06-12 18:40 ` Stephen Warren
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=51B767A8.7000506@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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).