From: Dominik Csapak <d.csapak@proxmox.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, eblake@redhat.com, armbru@redhat.com,
kwolf@redhat.com, mreitz@redhat.com
Subject: [Qemu-devel] [PATCH v3 0/3] qapi: return ShutdownCause for events
Date: Wed, 5 Dec 2018 12:01:28 +0100 [thread overview]
Message-ID: <20181205110131.23049-1-d.csapak@proxmox.com> (raw)
This series improves the QMP SHUTDOWN and RESET events by adding
the ShutdownCause as additional parameter and splitting
the HOST_QMP reason into HOST_QMP_QUIT and HOST_QMP_SYSTEM_RESET
to be able to detect the difference between them when using '--no-reboot'
this is an alternative to my previous patches[1][2] which
added an exit-script/added a 'reset' argument to the events
1: https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg00697.html
2: https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg01271.html
changes from v2:
* better wording for the iotest changes
* typo fix (ouput -> output)
* added a '(since 4.0)' to the reason in the events
changes from v1:
* explain the reason for the patches in more detail in commit messages
* better punctuation and wording in commit messages
* switched patch 2 and 3
* fix iotests after both 2 and 3
* added documentation for 'reason' in the SHUTDOWN/RESET events
(this was missing in v1)
Dominik Csapak (3):
qapi: Turn ShutdownCause into QAPI enum
qapi: Add reason to SHUTDOWN and RESET events
qapi: Split host-qmp into quit and system-reset
include/sysemu/sysemu.h | 20 --------------------
qapi/run-state.json | 44 ++++++++++++++++++++++++++++++++++++++++++--
qmp.c | 4 ++--
tests/qemu-iotests/060.out | 4 ++--
tests/qemu-iotests/071.out | 4 ++--
tests/qemu-iotests/081.out | 14 +++++++-------
tests/qemu-iotests/087.out | 12 ++++++------
tests/qemu-iotests/094.out | 2 +-
tests/qemu-iotests/109.out | 44 ++++++++++++++++++++++----------------------
tests/qemu-iotests/117.out | 2 +-
tests/qemu-iotests/119.out | 2 +-
tests/qemu-iotests/120.out | 2 +-
tests/qemu-iotests/127.out | 2 +-
tests/qemu-iotests/140.out | 2 +-
tests/qemu-iotests/143.out | 2 +-
tests/qemu-iotests/156.out | 2 +-
tests/qemu-iotests/176.out | 16 ++++++++--------
tests/qemu-iotests/183.out | 4 ++--
tests/qemu-iotests/184.out | 12 ++++++++----
tests/qemu-iotests/185.out | 10 +++++-----
tests/qemu-iotests/191.out | 6 ++++--
tests/qemu-iotests/195.out | 6 ++++--
tests/qemu-iotests/223.out | 2 +-
tests/qemu-iotests/227.out | 12 ++++++++----
vl.c | 4 ++--
25 files changed, 133 insertions(+), 101 deletions(-)
--
2.11.0
next reply other threads:[~2018-12-05 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 11:01 Dominik Csapak [this message]
2018-12-05 11:01 ` [Qemu-devel] [PATCH v3 1/3] qapi: Turn ShutdownCause into QAPI enum Dominik Csapak
2018-12-05 11:01 ` [Qemu-devel] [PATCH v3 2/3] qapi: Add reason to SHUTDOWN and RESET events Dominik Csapak
2018-12-05 11:01 ` [Qemu-devel] [PATCH v3 3/3] qapi: Split host-qmp into quit and system-reset Dominik Csapak
2018-12-05 12:21 ` [Qemu-devel] [PATCH v3 0/3] qapi: return ShutdownCause for events Markus Armbruster
2018-12-05 15:06 ` Dominik Csapak
2018-12-06 13:29 ` 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=20181205110131.23049-1-d.csapak@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).