qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Cc: mdroth@linux.vnet.ibm.com, armbru@redhat.com, dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/3] qmp: introduce query-wakeup-from-suspend-support command
Date: Wed, 6 Dec 2017 08:26:56 -0600	[thread overview]
Message-ID: <d3550f4f-adc1-ff8e-5aa7-7b1c815f2c90@redhat.com> (raw)
In-Reply-To: <20171206120217.11392-2-danielhb@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 994 bytes --]

On 12/06/2017 06:02 AM, Daniel Henrique Barboza wrote:
> When issuing the qmp/hmp 'system_wakeup' command, what happens in a
> nutshell is:
> 

> This patch implements a new QMP command called
> 'query-wakeup-from-suspend-support' that allows the caller to query
> if the guest supports wake up from suspend via system_wakeup. It
> goes over the subscribers of the wake up event and, if it's empty,
> it assumes that the guest does not support wake up from suspend
> (and thus, pm-suspend itself).
> 
> This is the expected output of the command when running a x86 guest:
> 
> {"execute" : "query-wakeup-from-suspend-support"}
> {"return": {"enabled": true}}

Do we really need a new command, or can we add it as an additional field
to an existing command (for example, in MachineInfo under
query-machines, or TargetInfo under query-target)?

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]

  reply	other threads:[~2017-12-06 14:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 12:02 [Qemu-devel] [PATCH 0/3] qmp/hmp: wakeup-from-suspend-support command Daniel Henrique Barboza
2017-12-06 12:02 ` [Qemu-devel] [PATCH 1/3] qmp: introduce query-wakeup-from-suspend-support command Daniel Henrique Barboza
2017-12-06 14:26   ` Eric Blake [this message]
2017-12-06 15:50     ` Daniel Henrique Barboza
2017-12-21 19:03       ` Daniel Henrique Barboza
2017-12-06 12:02 ` [Qemu-devel] [PATCH 2/3] hmp: introduce wakeup-from-suspend-support command Daniel Henrique Barboza
2017-12-06 12:02 ` [Qemu-devel] [PATCH 3/3] qga: update guest-suspend-ram and guest-suspend-hybrid descriptions Daniel Henrique Barboza
2017-12-21 19:23 ` [Qemu-devel] [PATCH 0/3] qmp/hmp: wakeup-from-suspend-support command no-reply

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=d3550f4f-adc1-ff8e-5aa7-7b1c815f2c90@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=danielhb@linux.vnet.ibm.com \
    --cc=dgilbert@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).