From: zhaoshenglong@huawei.com (Shannon Zhao)
To: linux-arm-kernel@lists.infradead.org
Subject: [Discussion] how to implement external power down for ARM
Date: Thu, 7 May 2015 21:02:02 +0800 [thread overview]
Message-ID: <554B624A.1010309@huawei.com> (raw)
In-Reply-To: <CAFEAcA_EJSm_OHxsGvDfydacHHz=RcvrHHCg_LEFpLCBUxHmtA@mail.gmail.com>
On 2015/5/7 20:34, 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 ACPI only tells guest to poweroff not reboot. I checked this on x86.
When using libvirt to start a VM, libvirt pass "-no-shutdown" to QEMU
that makes sure the QEMU process will not disappear when guest
poweroffs. When executing "virsh reboot VMname", libvirt send
"system_powerdown" to QEMU and when guest poweroffs libvirt send
"system_reset" to QEMU to restart VM.
So there is not a single external reboot command for ACPI.
>> And
>> reset doesn't depends on the guest, it just restart VM forcefully.
>> Reboot likes poweroff and start, while reset likes destroy and start.
>
> I (and QEMU) think there is no visible difference between
> poweroff-and-restart and destroy-recreate-and-restart...
>
It is different to guest.
--
Shannon
next prev parent reply other threads:[~2015-05-07 13:02 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
2015-05-07 13:02 ` Shannon Zhao [this message]
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=554B624A.1010309@huawei.com \
--to=zhaoshenglong@huawei.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).