qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Henrique Barboza <danielhb@linux.ibm.com>
To: qemu-devel@nongnu.org
Cc: mdroth@linux.vnet.ibm.com, armbru@redhat.com,
	dgilbert@redhat.com, eblake@redhat.com,
	Daniel Henrique Barboza <danielhb@linux.ibm.com>
Subject: [Qemu-devel] [PATCH v6 0/2] qmp: 'wakeup-suspend-support' in query-target
Date: Tue, 15 May 2018 11:09:42 -0300	[thread overview]
Message-ID: <20180515140944.15979-1-danielhb@linux.ibm.com> (raw)

v6:
- rebased with current master after being buried for a few months
- previous version link:
https://lists.gnu.org/archive/html/qemu-devel/2018-02/msg04882.html

v5:
- removed a paragraph in the recently added qemu_register_wakeup_notifier
comment that was added. That paragraph was adding too much in-depth
information about the current design of the system_wakeup, making it
harder to understand the whole point (suggested by Mike Roth).
- previous version link:
https://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg00879.html 

v4:
- added a comment in 'qemu_register_wakeup_notifier' about the effects
of adding a wakeup notifier without proper suspend/wakeup support in the
logic of the new wakeup-suspend-support flag, as suggested by Mike Roth
- previous version link:
https://lists.gnu.org/archive/html/qemu-devel/2018-01/msg00358.html

v3:
- added a "(since 2.12)" notation in the new flag, as suggested by
Eric Blake
- added a "backwards compatible" note in the commit msg
- previous version link:
https://lists.gnu.org/archive/html/qemu-devel/2018-01/msg00093.html

v2:
- changed the approach based on v1 discussions: instead of a new API, add
the required flag in QMP query-target
- dropped patch 2 since query-target does not have an HMP counterpart
- previous version link:
https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg00889.html


Daniel Henrique Barboza (2):
  qmp: adding 'wakeup-suspend-support' in query-target
  qga: update guest-suspend-ram and guest-suspend-hybrid descriptions

 arch_init.c             |  1 +
 include/sysemu/sysemu.h |  1 +
 qapi/misc.json          |  4 +++-
 qga/qapi-schema.json    | 14 ++++++++++----
 vl.c                    | 21 +++++++++++++++++++++
 5 files changed, 36 insertions(+), 5 deletions(-)

-- 
2.14.3

             reply	other threads:[~2018-05-15 14:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 14:09 Daniel Henrique Barboza [this message]
2018-05-15 14:09 ` [Qemu-devel] [PATCH v6 1/2] qmp: adding 'wakeup-suspend-support' in query-target Daniel Henrique Barboza
2018-05-15 15:45   ` Markus Armbruster
2018-05-16 13:13     ` Daniel Henrique Barboza
2018-05-17  8:44       ` Markus Armbruster
2018-05-17 12:35         ` Daniel Henrique Barboza
2018-05-15 14:09 ` [Qemu-devel] [PATCH v6 2/2] qga: update guest-suspend-ram and guest-suspend-hybrid descriptions Daniel Henrique Barboza
2018-05-15 15:35   ` Markus Armbruster
2018-05-16 13:49     ` Daniel Henrique Barboza
2018-05-17  8:26       ` 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=20180515140944.15979-1-danielhb@linux.ibm.com \
    --to=danielhb@linux.ibm.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=mdroth@linux.vnet.ibm.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).