From: Markus Armbruster <armbru@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"open list:Overall" <kvm@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel@nongnu.org, Cor nelia Huck <cornelia.huck@de.ibm.com>,
Gerd Hoffmann <kraxel@redhat.com>, Rob Herring <robh@kernel.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Alexander Graf <agraf@suse.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Anthony Perard <anthony.perard@citrix.com>,
"open list:X86" <xen-devel@lists.xenproject.org>,
David Gibson <david@gibson.dropbear.id.au>,
Artyom Tarasenko <atar4qemu@gmail.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Stefan Weil <sw@weilnetz.de>,
Alistair Francis <alistair.francis@xilinx.com>,
"open list:Calxeda Highbank" <qemu-arm@nongnu.org>,
Jan Kiszka <jan.kiszka@web.de>,
Paolo Bonzini <pbonzini@redhat.com>,
Scott Wood <scottwood@freescale.com>,
Richard Henderson <rth@twiddle.net>,
"Daniel P. Berrange" <berrange@redhat.com>,
Paul Burton <paul.burton@imgtec.com>,
Max Filippov <jcmvbkbc@gmail.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Michael Walle <michael@walle.cc>,
"open list:New World" <qemu-ppc@nongnu.org>,
Yongbok Kim <yongbok.kim@imgtec.com>,
Igor Mammedov <imammedo@redhat.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-arm] [Qemu-devel] [PATCH v2] event: Add source information to SHUTDOWN
Date: Thu, 20 Apr 2017 18:12:42 +0200 [thread overview]
Message-ID: <87r30n83d1.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <1f4e72ed-fab1-7099-768e-2a111df3a633@redhat.com> (Eric Blake's message of "Thu, 20 Apr 2017 08:20:11 -0500")
Eric Blake <eblake@redhat.com> writes:
> On 04/20/2017 07:09 AM, Daniel P. Berrange wrote:
>
>>>> +++ b/qapi/event.json
>>>> @@ -10,6 +10,10 @@
>>>> # Emitted when the virtual machine has shut down, indicating that qemu is
>>>> # about to exit.
>>>> #
>>>> +# @guest: If true, the shutdown was triggered by a guest request (such as
>>>> +# executing a halt instruction) rather than a host request (such as sending
>>>> +# qemu a SIGINT). (since 2.10)
>>>> +#
>>>
>>> "executing a halt instruction" suggests "halt" is a machine instruction.
>
> Which is indeed what most of the places I patched to pass 'true' are
> emulating - the machine halt instruction.
>
>>> I think you mean /usr/sbin/halt. Suggest something like "executing a
>>> halt command".
>>
>> Well technically /usr/sbin/halt just terminates all processes / kernel and
>> halts CPUs, but the virtual machine is still active (and a 'reset' in the
>> monitor can start it again. /usr/sbin/poweroff is what actually does the
>> ACPI poweroff to trigger QEMU to exit[1]
>
> I'm thinking of this wording:
>
> triggered by a guest request (such as the guest running
> /usr/sbin/poweroff to trigger an ACPI shutdown or machine halt instruction)
A quick glance at the patch suggests the instructions in question are
typically writes to some device register. I wouldn't call them "halt
instructions", in particular since there's the x86 "hlt" instruction
that does something else.
WARNING: multiple messages have this Message-ID (diff)
From: Markus Armbruster <armbru@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
"open list\:Overall" <kvm@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel@nongnu.org, Scott Wood <scottwood@freescale.com>,
Gerd Hoffmann <kraxel@redhat.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Rob Herring <robh@kernel.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Alexander Graf <agraf@suse.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Anthony Perard <anthony.perard@citrix.com>,
"open list\:X86" <xen-devel@lists.xenproject.org>,
Richard Henderson <rth@twiddle.net>,
Artyom Tarasenko <atar4qemu@gmail.com>,
Eduardo Habkost <ehabkost@redhat
Subject: Re: [Qemu-devel] [PATCH v2] event: Add source information to SHUTDOWN
Date: Thu, 20 Apr 2017 18:12:42 +0200 [thread overview]
Message-ID: <87r30n83d1.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <1f4e72ed-fab1-7099-768e-2a111df3a633@redhat.com> (Eric Blake's message of "Thu, 20 Apr 2017 08:20:11 -0500")
Eric Blake <eblake@redhat.com> writes:
> On 04/20/2017 07:09 AM, Daniel P. Berrange wrote:
>
>>>> +++ b/qapi/event.json
>>>> @@ -10,6 +10,10 @@
>>>> # Emitted when the virtual machine has shut down, indicating that qemu is
>>>> # about to exit.
>>>> #
>>>> +# @guest: If true, the shutdown was triggered by a guest request (such as
>>>> +# executing a halt instruction) rather than a host request (such as sending
>>>> +# qemu a SIGINT). (since 2.10)
>>>> +#
>>>
>>> "executing a halt instruction" suggests "halt" is a machine instruction.
>
> Which is indeed what most of the places I patched to pass 'true' are
> emulating - the machine halt instruction.
>
>>> I think you mean /usr/sbin/halt. Suggest something like "executing a
>>> halt command".
>>
>> Well technically /usr/sbin/halt just terminates all processes / kernel and
>> halts CPUs, but the virtual machine is still active (and a 'reset' in the
>> monitor can start it again. /usr/sbin/poweroff is what actually does the
>> ACPI poweroff to trigger QEMU to exit[1]
>
> I'm thinking of this wording:
>
> triggered by a guest request (such as the guest running
> /usr/sbin/poweroff to trigger an ACPI shutdown or machine halt instruction)
A quick glance at the patch suggests the instructions in question are
typically writes to some device register. I wouldn't call them "halt
instructions", in particular since there's the x86 "hlt" instruction
that does something else.
WARNING: multiple messages have this Message-ID (diff)
From: Markus Armbruster <armbru@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
"open list:Overall" <kvm@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel@nongnu.org, Scott Wood <scottwood@freescale.com>,
Gerd Hoffmann <kraxel@redhat.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Rob Herring <robh@kernel.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Alexander Graf <agraf@suse.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Anthony Perard <anthony.perard@citrix.com>,
"open list:X86" <xen-devel@lists.xenproject.org>,
Richard Henderson <rth@twiddle.net>,
Artyom Tarasenko <atar4qemu@gmail.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Stefan Weil <sw@weilnetz.de>,
Alistair Francis <alistair.francis@xilinx.com>,
"open list:Calxeda Highbank" <qemu-arm@nongnu.org>,
Jan Kiszka <jan.kiszka@web.de>,
Igor Mammedov <imammedo@redhat.com>,
Cor nelia Huck <cornelia.huck@de.ibm.com>,
David Gibson <david@gibson.dropbear.id.au>,
Paul Burton <paul.burton@imgtec.com>,
Max Filippov <jcmvbkbc@gmail.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Michael Walle <michael@walle.cc>,
"open list:New World" <qemu-ppc@nongnu.org>,
Yongbok Kim <yongbok.kim@imgtec.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH v2] event: Add source information to SHUTDOWN
Date: Thu, 20 Apr 2017 18:12:42 +0200 [thread overview]
Message-ID: <87r30n83d1.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <1f4e72ed-fab1-7099-768e-2a111df3a633@redhat.com> (Eric Blake's message of "Thu, 20 Apr 2017 08:20:11 -0500")
Eric Blake <eblake@redhat.com> writes:
> On 04/20/2017 07:09 AM, Daniel P. Berrange wrote:
>
>>>> +++ b/qapi/event.json
>>>> @@ -10,6 +10,10 @@
>>>> # Emitted when the virtual machine has shut down, indicating that qemu is
>>>> # about to exit.
>>>> #
>>>> +# @guest: If true, the shutdown was triggered by a guest request (such as
>>>> +# executing a halt instruction) rather than a host request (such as sending
>>>> +# qemu a SIGINT). (since 2.10)
>>>> +#
>>>
>>> "executing a halt instruction" suggests "halt" is a machine instruction.
>
> Which is indeed what most of the places I patched to pass 'true' are
> emulating - the machine halt instruction.
>
>>> I think you mean /usr/sbin/halt. Suggest something like "executing a
>>> halt command".
>>
>> Well technically /usr/sbin/halt just terminates all processes / kernel and
>> halts CPUs, but the virtual machine is still active (and a 'reset' in the
>> monitor can start it again. /usr/sbin/poweroff is what actually does the
>> ACPI poweroff to trigger QEMU to exit[1]
>
> I'm thinking of this wording:
>
> triggered by a guest request (such as the guest running
> /usr/sbin/poweroff to trigger an ACPI shutdown or machine halt instruction)
A quick glance at the patch suggests the instructions in question are
typically writes to some device register. I wouldn't call them "halt
instructions", in particular since there's the x86 "hlt" instruction
that does something else.
next prev parent reply other threads:[~2017-04-20 16:13 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 22:22 [PATCH v2] event: Add source information to SHUTDOWN Eric Blake
2017-04-19 22:22 ` [Qemu-devel] " Eric Blake
2017-04-19 22:22 ` Eric Blake
2017-04-19 22:36 ` [Qemu-devel] " Alistair Francis
2017-04-19 22:36 ` Alistair Francis
2017-04-20 1:11 ` Eric Blake
2017-04-20 1:11 ` [Qemu-arm] " Eric Blake
2017-04-20 1:11 ` Eric Blake
2017-04-20 1:11 ` Eric Blake
2017-04-19 22:36 ` Alistair Francis
2017-04-20 11:59 ` Markus Armbruster
2017-04-20 11:59 ` Markus Armbruster
2017-04-20 11:59 ` Markus Armbruster
2017-04-20 12:09 ` Daniel P. Berrange
2017-04-20 12:09 ` Daniel P. Berrange
2017-04-20 12:09 ` Daniel P. Berrange
2017-04-20 13:20 ` Eric Blake
2017-04-20 13:20 ` Eric Blake
2017-04-20 13:20 ` Eric Blake
2017-04-20 13:20 ` Eric Blake
2017-04-20 16:12 ` Markus Armbruster [this message]
2017-04-20 16:12 ` Markus Armbruster
2017-04-20 16:12 ` Markus Armbruster
2017-04-20 18:12 ` Eric Blake
2017-04-20 18:12 ` Eric Blake
2017-04-20 18:12 ` Eric Blake
2017-04-20 18:12 ` Eric Blake
2017-04-20 16:12 ` Markus Armbruster
2017-04-20 13:31 ` Eric Blake
2017-04-20 13:31 ` Eric Blake
2017-04-20 13:31 ` Eric Blake
2017-04-20 13:31 ` Eric Blake
2017-04-20 16:18 ` [Qemu-arm] " Markus Armbruster
2017-04-20 16:18 ` Markus Armbruster
2017-04-20 16:18 ` Markus Armbruster
2017-04-20 19:05 ` Eric Blake
2017-04-20 19:05 ` Eric Blake
2017-04-20 19:05 ` Eric Blake
2017-04-20 19:05 ` Eric Blake
2017-04-20 22:55 ` Alistair Francis
2017-04-20 22:55 ` Alistair Francis
2017-04-20 22:55 ` Alistair Francis
2017-04-20 11:59 ` Markus Armbruster
2017-04-20 20:28 ` Eric Blake
2017-04-20 20:28 ` Eric Blake
2017-04-20 20:28 ` Eric Blake
2017-04-20 20:28 ` Eric Blake
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=87r30n83d1.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=agraf@suse.de \
--cc=alistair.francis@xilinx.com \
--cc=anthony.perard@citrix.com \
--cc=atar4qemu@gmail.com \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=jan.kiszka@web.de \
--cc=jcmvbkbc@gmail.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=michael@walle.cc \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=paul.burton@imgtec.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=robh@kernel.org \
--cc=rth@twiddle.net \
--cc=scottwood@freescale.com \
--cc=sstabellini@kernel.org \
--cc=sw@weilnetz.de \
--cc=xen-devel@lists.xenproject.org \
--cc=yongbok.kim@imgtec.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.