All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Dominik Csapak <d.csapak@proxmox.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, pbonzini@redhat.com,
	mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/3] qapi: move ShutdownCause to qapi/run-state.json
Date: Fri, 30 Nov 2018 10:15:36 +0100	[thread overview]
Message-ID: <871s73lydj.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <87efb3lz2r.fsf@dusky.pond.sub.org> (Markus Armbruster's message of "Fri, 30 Nov 2018 10:00:28 +0100")

One more thing...

Markus Armbruster <armbru@redhat.com> writes:

> Dominik Csapak <d.csapak@proxmox.com> writes:
>
>> this makes it possible to use the reason as return value
>> in a QMP event, such as SHUTDOWN
>
> Please start your sentences with a capital letter and end them with
> punctuation.
>
> The patch's purpose could perhaps be stated a bit more clearly.  Let me
> try:
>
>   qapi: Turn ShutdownCause into a QAPI enum
>
>   Needed so the patch after next can add ShutdownCause to QMP events
>   SHUTDOWN and RESET.
>
>> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
>> ---
>>  include/sysemu/sysemu.h | 20 --------------------
>>  qapi/run-state.json     | 33 +++++++++++++++++++++++++++++++++
>>  2 files changed, 33 insertions(+), 20 deletions(-)
>>
>> diff --git a/include/sysemu/sysemu.h b/include/sysemu/sysemu.h
>> index 8d6095d98b..f83522c7e7 100644
>> --- a/include/sysemu/sysemu.h
>> +++ b/include/sysemu/sysemu.h
>> @@ -31,26 +31,6 @@ VMChangeStateEntry *qemu_add_vm_change_state_handler(VMChangeStateHandler *cb,
>>  void qemu_del_vm_change_state_handler(VMChangeStateEntry *e);
>>  void vm_state_notify(int running, RunState state);
>>  
>> -/* Enumeration of various causes for shutdown. */
>> -typedef enum ShutdownCause {
>> -    SHUTDOWN_CAUSE_NONE,          /* No shutdown request pending */
>> -    SHUTDOWN_CAUSE_HOST_ERROR,    /* An error prevents further use of guest */
>> -    SHUTDOWN_CAUSE_HOST_QMP,      /* Reaction to a QMP command, like 'quit' */
>> -    SHUTDOWN_CAUSE_HOST_SIGNAL,   /* Reaction to a signal, such as SIGINT */
>> -    SHUTDOWN_CAUSE_HOST_UI,       /* Reaction to UI event, like window close */
>> -    SHUTDOWN_CAUSE_GUEST_SHUTDOWN,/* Guest shutdown/suspend request, via
>> -                                     ACPI or other hardware-specific means */
>> -    SHUTDOWN_CAUSE_GUEST_RESET,   /* Guest reset request, and command line
>> -                                     turns that into a shutdown */
>> -    SHUTDOWN_CAUSE_GUEST_PANIC,   /* Guest panicked, and command line turns
>> -                                     that into a shutdown */
>> -    SHUTDOWN_CAUSE_SUBSYSTEM_RESET,/* Partial guest reset that does not trigger
>> -                                      QMP events and ignores --no-reboot. This
>> -                                      is useful for sanitize hypercalls on s390
>> -                                      that are used during kexec/kdump/boot */
>> -    SHUTDOWN_CAUSE__MAX,
>> -} ShutdownCause;
>> -
>>  static inline bool shutdown_caused_by_guest(ShutdownCause cause)
>>  {
>>      return cause >= SHUTDOWN_CAUSE_GUEST_SHUTDOWN;

Because of this, order matters.  Your patch moves the enumeration away,
so readers get even less of a chance to catch this.

>> diff --git a/qapi/run-state.json b/qapi/run-state.json
>> index 332e44897b..883bed167c 100644
>> --- a/qapi/run-state.json
>> +++ b/qapi/run-state.json
>> @@ -60,6 +60,39 @@
>>              'guest-panicked', 'colo', 'preconfig' ] }
>>  
>>  ##
>> +# @ShutdownCause:
>> +#
>> +# An enumeration of reasons for a Shutdown.
>> +#
>> +# @none: No shutdown request pending
>> +#
>> +# @host-error: An error prevented further use of guest
>
> Any particular reason for changing the tense from "prevents" to
> "prevented"?
>
>> +#
>> +# @host-qmp: Reaction to a QMP command, like 'quit'
>> +#
>> +# @host-signal: Reaction to a signal, such as SIGINT
>> +#
>> +# @host-ui: Reaction to a UI event, like window close
>> +#
>> +# @guest-shutdown: Guest shutdown/suspend request, via ACPI or other
>> +#                  hardware-specific means
>> +#
>> +# @guest-reset: Guest reset request, and command line turns that into
>> +#               a shutdown
>> +#
>> +# @guest-panic: Guest panicked, and command line turns that into a shutdown
>> +#
>> +# @subsystem-reset: Partial guest reset that does not trigger QMP events and
>> +#                  ignores --no-reboot. This is useful for sanitizing
>> +#                  hypercalls on s390 that are used during kexec/kdump/boot
>> +#
>> +##
>> +{ 'enum': 'ShutdownCause',

Let's add

       # Beware, shutdown_caused_by_guest() depends on enumeration order

here.  Adding it to the doc comment above would be no good, because
that's external documentation (it would end up in the QEMU QMP reference
manual).

>> +  'data': [ 'none', 'host-error', 'host-qmp', 'host-signal', 'host-ui',
>> +            'guest-shutdown', 'guest-reset', 'guest-panic',
>> +            'subsystem-reset'] }
>> +
>> +##
>>  # @StatusInfo:
>>  #
>>  # Information about VCPU run state

  reply	other threads:[~2018-11-30  9:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 11:52 [Qemu-devel] [PATCH 0/3] qapi: return ShutdownCause for events Dominik Csapak
2018-10-31 11:52 ` [Qemu-devel] [PATCH 1/3] qapi: move ShutdownCause to qapi/run-state.json Dominik Csapak
2018-11-30  9:00   ` Markus Armbruster
2018-11-30  9:15     ` Markus Armbruster [this message]
2018-10-31 11:52 ` [Qemu-devel] [PATCH 2/3] qapi: split host-qmp into quit and system-reset Dominik Csapak
2018-11-30  9:41   ` Markus Armbruster
2018-11-30 13:20     ` Dominik Csapak
2018-11-30 13:55       ` Eric Blake
2018-10-31 11:52 ` [Qemu-devel] [PATCH 3/3] qapi: add reason to SHUTDOWN and RESET events Dominik Csapak
2018-11-30  9:43   ` Markus Armbruster
2018-11-19 13:45 ` [Qemu-devel] [PATCH 0/3] qapi: return ShutdownCause for events Dominik Csapak

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=871s73lydj.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=d.csapak@proxmox.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 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.