From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [Discussion] how to implement external power down for ARM
Date: Thu, 07 May 2015 14:48:39 +0200 [thread overview]
Message-ID: <2710086.QZJtQiM3YX@wuerfel> (raw)
In-Reply-To: <CAFEAcA_EJSm_OHxsGvDfydacHHz=RcvrHHCg_LEFpLCBUxHmtA@mail.gmail.com>
On Thursday 07 May 2015 13:34:10 Peter Maydell wrote:
> On 7 May 2015 at 13:18, Shannon Zhao <zhaoshenglong@huawei.com> wrote:
> > On 2015/5/7 20:12, Peter Maydell wrote:
> >> On 7 May 2015 at 13:10, Shannon Zhao <zhaoshenglong@huawei.com> wrote:
> >>> BTW, IIUC QEMU doesn't support the gracefully reboot support. The reboot
> >>> depends on libvirt or other management tools. So the reboot case in
> >>> virtualization is firstly poweroff, then start again.
> >>
> >> I'm not sure what you mean by this -- QEMU supports 'reset this
> >> VM' at the machine emulation level, so if we can tell the guest
> >> to reboot then it should as part of this process issue the
> >> PSCI SYSTEM_RESET command, which QEMU/KVM will then handle
> >> to do a reset of the VM.
>
> > Yes, QEMU supports reset, but doesn't support (gracefully) reboot.
>
> Isn't that what this ACPI work is about? Tell the guest to initiate
> a graceful reboot, and then the guest will tell QEMU to reboot
> the emulated h/w when it's ready.
>
The problem here is user space: acpid only listens for KEY_POWER
events, not KEY_RESTART. This means graceful shutdown works as
expected, but graceful reboot requires a process that listens
to the input device and calls /sbin/reboot if it KEY_RESTART
appears. I think that can be done by adding a configuration file
in /etc/acpi/events/, but it's not there by default because PCs
only have a power button and no reset button (they use CTRL+ALT+DEL
on the keyboard for that).
Arnd
next prev parent reply other threads:[~2015-05-07 12:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 1:03 [Discussion] how to implement external power down for ARM Shannon Zhao
2015-04-30 8:03 ` Arnd Bergmann
2015-04-30 9:08 ` Peter Maydell
2015-04-30 9:19 ` Arnd Bergmann
2015-04-30 9:29 ` Mark Rutland
2015-04-30 9:56 ` Arnd Bergmann
2015-05-04 2:09 ` Shannon Zhao
2015-05-04 15:49 ` Arnd Bergmann
2015-05-05 2:57 ` Joel Stanley
2015-05-05 9:53 ` Arnd Bergmann
2015-05-05 10:51 ` Christoffer Dall
2015-05-05 10:55 ` Arnd Bergmann
2015-05-05 11:13 ` Shannon Zhao
2015-05-06 6:56 ` Shannon Zhao
2015-05-06 7:29 ` Arnd Bergmann
2015-05-06 8:19 ` Shannon Zhao
2015-05-06 8:37 ` Arnd Bergmann
2015-05-06 8:41 ` Shannon Zhao
2015-05-06 10:14 ` Christoffer Dall
2015-05-07 2:39 ` Shannon Zhao
2015-05-07 8:55 ` Arnd Bergmann
2015-05-07 9:18 ` Shannon Zhao
2015-05-07 9:43 ` Arnd Bergmann
2015-05-07 12:10 ` Shannon Zhao
2015-05-07 12:12 ` Peter Maydell
2015-05-07 12:18 ` Shannon Zhao
2015-05-07 12:34 ` Peter Maydell
2015-05-07 12:48 ` Arnd Bergmann [this message]
2015-05-07 13:02 ` Shannon Zhao
2015-04-30 13:38 ` Hanjun Guo
2015-05-04 1:55 ` Shannon Zhao
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=2710086.QZJtQiM3YX@wuerfel \
--to=arnd@arndb.de \
--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