From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Stop secondary cpus in machine_halt()
Date: Fri, 2 Jul 2010 00:11:28 +0100 [thread overview]
Message-ID: <20100701231128.GA19906@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100701224706.GA26473@lixom.net>
On Thu, Jul 01, 2010 at 05:47:06PM -0500, Olof Johansson wrote:
> ARM doesn't spin down secondary cpus on halt, which results in interrupts
> being delivered even after the "System halted" message, etc.
>
> Change that to use smp_send_stop() to halt them. Also, change the
> smp_send_stop() on ARM to not do a stack dump when stopping.
Actually, we want stack dumps - sometimes. For instance, when we
panic() or similar.
next prev parent reply other threads:[~2010-07-01 23:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 22:47 [PATCH] ARM: Stop secondary cpus in machine_halt() Olof Johansson
2010-07-01 23:11 ` Russell King - ARM Linux [this message]
2010-07-02 0:10 ` Olof Johansson
2010-07-03 18:46 ` [PATCH v2] " Olof Johansson
2010-07-12 16:48 ` Russell King - ARM Linux
2010-07-26 12:31 ` Russell King - ARM Linux
2010-07-26 15:26 ` Olof Johansson
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=20100701231128.GA19906@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).