From: Joel Stanley <joel@jms.id.au>
To: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
sparclinux@vger.kernel.org
Cc: fabf@skynet.be, akpm@linux-foundation.org,
benh@kernel.crashing.org, mpe@ellerman.id.au,
rusty@rustcorp.com.au, jk@ozlabs.org, davem@davemloft.net
Subject: [PATCH v2 3/3] powerpc/powernv: Reboot when requested by firmware
Date: Wed, 1 Apr 2015 17:34:48 +1030 [thread overview]
Message-ID: <1427871888-27331-3-git-send-email-joel@jms.id.au> (raw)
In-Reply-To: <1427871888-27331-1-git-send-email-joel@jms.id.au>
Use orderly_reboot so userspace will to shut itself down via the reboot
path. This is required for graceful reboot initiated by the BMC, such
as when a user uses ipmitool to issue a 'chassis power cycle' command.
Signed-off-by: Joel Stanley <joel@jms.id.au>
Acked-by: Michael Ellerman <mpe@ellerman.id.au>
---
arch/powerpc/platforms/powernv/opal-power.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/opal-power.c b/arch/powerpc/platforms/powernv/opal-power.c
index 48bf5b0..ac46c2c 100644
--- a/arch/powerpc/platforms/powernv/opal-power.c
+++ b/arch/powerpc/platforms/powernv/opal-power.c
@@ -29,8 +29,9 @@ static int opal_power_control_event(struct notifier_block *nb,
switch (type) {
case SOFT_REBOOT:
- /* Fall through. The service processor is responsible for
- * bringing the machine back up */
+ pr_info("OPAL: reboot requested\n");
+ orderly_reboot();
+ break;
case SOFT_OFF:
pr_info("OPAL: poweroff requested\n");
orderly_poweroff(true);
--
2.1.4
next prev parent reply other threads:[~2015-04-01 7:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 7:04 [PATCH v2 1/3] envctrl: Ignore orderly_poweroff return value Joel Stanley
2015-04-01 7:04 ` [PATCH v2 2/3] kernel/reboot.c: Add orderly_reboot for graceful reboot Joel Stanley
2015-04-01 22:27 ` Julian Calaby
2015-04-01 7:04 ` Joel Stanley [this message]
2015-04-01 16:18 ` [PATCH v2 1/3] envctrl: Ignore orderly_poweroff return value David Miller
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=1427871888-27331-3-git-send-email-joel@jms.id.au \
--to=joel@jms.id.au \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=fabf@skynet.be \
--cc=jk@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=rusty@rustcorp.com.au \
--cc=sparclinux@vger.kernel.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).