qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RfC PATCH 0/5] console: qom-ify & extent screendump mo


From: Eric Blake
Subject: Re: [Qemu-devel] [RfC PATCH 0/5] console: qom-ify & extent screendump monitor command
Date: Thu, 18 Apr 2013 06:10:19 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130402 Thunderbird/17.0.5

On 04/18/2013 03:01 AM, Gerd Hoffmann wrote:
>   Hi,
> 
> This patch qom-ifies the QemuConsoles and adds an new, optional
> parameter to the screendump command to specify the device you
> want dump from.
> 
> Question for the QOM guys: where in the tree should the QemuConsoles
> show up?  I can't find anything in the tree doing this.  I've placed
> them below /backend.  See patch #2.  Ok?  Better suggestions?
> 
> Question for the libvirt guys:  Is it ok for libvirt to just extend the
> existing screendump command?  Can libvirt figure there is a new
> (optional) parameter?  See patch #5.

The existing libvirt API is:

char *
virDomainScreenshot(virDomainPtr domain,
                    virStreamPtr stream,
                    unsigned int screen,
                    unsigned int flags)

which uses the screen argument to distinguish both between devices and
heads on a given device:

 * The screen ID is the sequential number of screen. In case of multiple
 * graphics cards, heads are enumerated before devices, e.g. having
 * two graphics cards, both with four heads, screen ID 5 addresses
 * the second head on the second card.

So yes, I think libvirt will be able to drive the new command by knowing
how many heads appear per device, then passing in the appropriate named
device to the QMP command.  And yes, I'll review patch 5 regarding
interface design.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]