qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
	qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Cc: "Markus Armbruster" <armbru@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Jiri Denemark" <jdenemar@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] Allow to specify a display device ID and head whith the screendump command
Date: Mon, 5 Mar 2018 09:37:18 -0600	[thread overview]
Message-ID: <5483b6f9-32ac-4d20-9e21-c784a639c62c@redhat.com> (raw)
In-Reply-To: <1520248105-10053-1-git-send-email-thuth@redhat.com>

On 03/05/2018 05:08 AM, Thomas Huth wrote:

In the subject line: s/whith/with/

Also, it's rather long (over 75 characters, while typical messages are 
under 65, since it is nice to still fit in 80 columns even when 'git 
log' adds indentation), better might be:

qapi: Add parameters to screendump

then go into details about the parameters in the commit body

> QEMU's screendump command can only take dumps from the primary display.
> When using multiple VGA cards, there is no way to get a dump from a
> secondary card or other display heads yet. So let's add an 'device' and
> a 'head' parameter to the HMP and QMP commands to be able to specify
> alternative devices and heads with the screendump command, too.
> 
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> Acked-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>   v3:
>   - Drop redundant qemu_console_lookup_by_index(0);
>   - Remove trailing "." from error message
> 

> +++ b/qapi/ui.json
> @@ -77,6 +77,10 @@
>   #
>   # @filename: the path of a new PPM file to store the image
>   #
> +# @device: ID of the display device that should be used (since 2.12)

Worth mentioning how the default value is computed?

> +#
> +# @head: head to use in case the device supports multiple heads (since 2.12)
> +#
>   # Returns: Nothing on success
>   #
>   # Since: 0.14.0
> @@ -88,7 +92,8 @@
>   # <- { "return": {} }
>   #
>   ##
> -{ 'command': 'screendump', 'data': {'filename': 'str'} }
> +{ 'command': 'screendump',
> +  'data': {'filename': 'str', '*device': 'str', '*head': 'int'} }
>   

QAPI changes are reasonable from a UI point of view.

> +    } else {
> +        if (has_head) {
> +            error_setg(errp, "'head' must be specified together with 'device'");

This isn't documented.

> +            return;
> +        }
> +        con = qemu_console_lookup_by_index(0);
> +        if (!con) {
> +            error_setg(errp, "There is no console to take a screendump from");
> +            return;
> +        }
>       }
>   
>       graphic_hw_update(con);
> 

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

      parent reply	other threads:[~2018-03-05 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05 11:08 [Qemu-devel] [PATCH v3] Allow to specify a display device ID and head whith the screendump command Thomas Huth
2018-03-05 12:46 ` Gerd Hoffmann
2018-03-05 15:37 ` Eric Blake [this message]

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=5483b6f9-32ac-4d20-9e21-c784a639c62c@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=jdenemar@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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).