qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, armbru@redhat.com,
	mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/3] qapi: Turn ShutdownCause into QAPI enum
Date: Tue, 4 Dec 2018 08:25:45 +0100	[thread overview]
Message-ID: <1af51d35-f74d-cc80-9f87-44cb0d82c92d@proxmox.com> (raw)
In-Reply-To: <5091fc5e-51f0-d470-de1c-c75ad0314d42@redhat.com>

On 12/3/18 10:34 PM, Eric Blake wrote:
> On 12/3/18 3:26 AM, Dominik Csapak wrote:
>> 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     | 34 ++++++++++++++++++++++++++++++++++
>>   2 files changed, 34 insertions(+), 20 deletions(-)
> 
>> +++ b/qapi/run-state.json
> 
>> +# @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
> 
> Is it ever possible for a user to see this state, or is the intent that 
> it is internal-only?  But it's not the first time we've leaked internal 
> states into enums (see, for example, 'null' within JobStatus in 
> job.json), so it's not a showstopper.
> 

afaics, it is not possible to get this via an event, but i wanted
to keep the comment somehow.
should i mark it with an '(internal only)' or something similar?

  reply	other threads:[~2018-12-04  7:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03  9:26 [Qemu-devel] [PATCH v2 0/3] qapi: return ShutdownCause for events Dominik Csapak
2018-12-03  9:26 ` [Qemu-devel] [PATCH v2 1/3] qapi: Turn ShutdownCause into QAPI enum Dominik Csapak
2018-12-03 12:23   ` Markus Armbruster
2018-12-03 21:34   ` Eric Blake
2018-12-04  7:25     ` Dominik Csapak [this message]
2018-12-03  9:26 ` [Qemu-devel] [PATCH v2 2/3] qapi: Add reason to SHUTDOWN and RESET events Dominik Csapak
2018-12-03 12:26   ` Markus Armbruster
2018-12-03 21:30     ` Eric Blake
2018-12-04  5:37       ` Markus Armbruster
2018-12-03 21:36   ` Eric Blake
2018-12-04  7:26     ` Dominik Csapak
2018-12-03  9:26 ` [Qemu-devel] [PATCH v2 3/3] qapi: Split host-qmp into quit and system-reset Dominik Csapak
2018-12-03 12:28   ` Markus Armbruster
2018-12-03 21:38   ` Eric Blake
2018-12-04  7:27     ` Dominik Csapak
2018-12-03 12:29 ` [Qemu-devel] [PATCH v2 0/3] qapi: return ShutdownCause for events Markus Armbruster

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=1af51d35-f74d-cc80-9f87-44cb0d82c92d@proxmox.com \
    --to=d.csapak@proxmox.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.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 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).