From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: call disable_nonboot_cpus() from machine_shutdown()
Date: Sun, 6 Jan 2013 16:22:00 +0000 [thread overview]
Message-ID: <20130106162200.GC11025@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <50E5E967.3020805@wwwdotorg.org>
On Thu, Jan 03, 2013 at 08:26:15PM +0000, Stephen Warren wrote:
> On 01/03/2013 05:21 AM, Russell King - ARM Linux wrote:
> > On Thu, Jan 03, 2013 at 12:02:59PM +0000, Will Deacon wrote:
> >> You need the smp_send_stop call in order to send the cpu_kill (looks like
> >> tegra needs die and then kill). So you really need hotplug support as well
> >> as suspend for this to do much (if not, the secondaries end up spinning
> >> with interrupts disabled which is probably the best we can do anyway).
> >>
> >> We could add SUSPEND as a KEXEC dependency if SMP (we already have HOTPLUG
> >> there) if you like?
> >
> > Or we could look into bringing in the code to do this when KEXEC is
> > enabled - which would mean an amount of restructuring of the Kconfig
> > files.
>
> I'm not sure if any of this thread means we should hold off on this
> patch, or just that the Kconfig could/should be enhanced later?
Well, Russell's suggestion looked easy enough to have a crack out so you
could always post a series implementing it along with this patch.
> One thing I did just notice with my patch: disable_nonboot_cpus() ends
> up being called twice for the poweroff path:
>
> [ 30.461847] Disabling non-boot CPUs ...
> [ 30.478797] CPU1: shutdown
> [ 30.492104] Power down.
> [ 30.494578] Disabling non-boot CPUs ...
>
> Is this worth worrying about?
It's harmless but it's also pretty horrible. Unfortunately, I don't see
what we can do about it: it's a direct side-effect of generic code calling
disable_nonboot_cpus for poweroff and not for kexec.
Will
next prev parent reply other threads:[~2013-01-06 16:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 21:07 [PATCH] ARM: call disable_nonboot_cpus() from machine_shutdown() Stephen Warren
2013-01-02 21:52 ` Russell King - ARM Linux
2013-01-02 23:59 ` Stephen Boyd
2013-01-03 12:02 ` Will Deacon
2013-01-03 12:21 ` Russell King - ARM Linux
2013-01-03 18:08 ` Jason Gunthorpe
2013-01-03 20:26 ` Stephen Warren
2013-01-06 16:22 ` Will Deacon [this message]
2013-01-06 16:40 ` Russell King - ARM Linux
2013-01-07 1:53 ` Eric W. Biederman
2013-01-07 14:25 ` Will Deacon
2013-01-07 14:48 ` Russell King - ARM Linux
2013-01-11 5:59 ` Eric W. Biederman
2013-01-11 10:04 ` Russell King - ARM Linux
2013-01-29 22:01 ` Stephen Warren
2013-01-09 0:06 ` Stephen Warren
2013-01-11 6:28 ` Eric W. Biederman
2013-01-29 22:10 ` Stephen Warren
2013-01-03 12:03 ` 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=20130106162200.GC11025@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--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).