From: Andrew Morton <akpm@linux-foundation.org>
To: Joel Stanley <joel@jms.id.au>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
fabf@skynet.be, benh@kernel.crashing.org, mpe@ellerman.id.au,
rusty@rustcorp.com.au, jk@ozlabs.org
Subject: Re: [PATCH 1/2] kernel/reboot.c: Add orderly_reboot for graceful reboot
Date: Tue, 31 Mar 2015 15:39:12 -0700 [thread overview]
Message-ID: <20150331153912.267c0b1af94b5f4964d791de@linux-foundation.org> (raw)
In-Reply-To: <1427681733-25488-1-git-send-email-joel@jms.id.au>
On Mon, 30 Mar 2015 12:45:32 +1030 Joel Stanley <joel@jms.id.au> wrote:
> The kernel has orderly_poweroff which allows the kernel to initiate a
> graceful shutdown of userspace, by running /sbin/poweroff. This adds
> orderly_reboot that will cause userspace to shut itself down by calling
> /sbin/reboot.
>
> This will be used for shutdown initiated by a system controller on
> platforms that do not use ACPI.
gee. There are a lot of callers of emergency_restart(). Why is the
BMC reboot special, and how many of the emergency_restart() callers
really be using orderly_reboot()?
We have /proc/sys/kernel/poweroff_cmd. Should we have
/proc/sys/kernel/reboot_cmd as well? If not,
kernel/reboot.c:reboot_cmd[] can be made static ;)
next prev parent reply other threads:[~2015-03-31 22:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 2:15 Joel Stanley
2015-03-30 2:15 ` [PATCH 2/2] powerpc/powernv: Reboot when requested by firmware Joel Stanley
2015-03-30 5:32 ` Michael Ellerman
2015-03-31 22:39 ` Andrew Morton [this message]
2015-04-01 3:17 ` [PATCH 1/2] kernel/reboot.c: Add orderly_reboot for graceful reboot Joel Stanley
2015-04-01 5:05 ` Anshuman Khandual
2015-04-01 4:52 ` Anshuman Khandual
2015-04-01 5:03 ` Andrew Morton
2015-04-01 5:05 ` Andrew Morton
2015-04-01 5:32 ` Joel Stanley
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=20150331153912.267c0b1af94b5f4964d791de@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=fabf@skynet.be \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®