qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: kwolf@redhat.com, aliguori@us.ibm.com, stefanha@gmail.com,
	qemu-devel@nongnu.org, lcapitulino@redhat.com,
	pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH V7 08/14] qmp: add interface query-images.
Date: Mon, 04 Mar 2013 10:30:52 +0800	[thread overview]
Message-ID: <5134075C.7070601@linux.vnet.ibm.com> (raw)
In-Reply-To: <512EBD01.8010906@linux.vnet.ibm.com>

>>>    
>>>    ##
>>> +# @query-images:
>>> +#
>>> +# Get a list of DeviceImageInfo for all virtual block devices.
>>
>> # Get block device image information
>>
>    OK.
> 
>>> +#
>>> +# @device: #optional the name of the device to get image info from. If not
>>> +#          specified, all block devices will be queried
>>> +# @backing: #optional true to show information on backing images, false or
>>> +#          omitted to show just the top image of a block device
>>
>> I'm not sure these flags are necessary.
>>
>    These flag seems more flex to me. Always querying all info require
> caller do a filter operation on what he got, but in many times caller
> may be interested on only one device.
>
  Coding for next version, I still feel flag may bring flexbility.
Markus, are u OK with this?


>>> +#
>>> +# Returns: a list of @DeviceImageInfo describing each virtual block device
>>> +#
>>> +# Since: 1.5
>>> +##
>>> +{ 'command': 'query-images',
>>> +  'data': { '*device': 'str', '*backing': 'bool' },
>>> +  'returns': ['DeviceImageInfo'] }
>>> +



-- 
Best Regards

Wenchao Xia

       reply	other threads:[~2013-03-04  2:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1361875228-15769-1-git-send-email-xiawenc@linux.vnet.ibm.com>
     [not found] ` <1361875228-15769-9-git-send-email-xiawenc@linux.vnet.ibm.com>
     [not found]   ` <878v69hhl5.fsf@blackfin.pond.sub.org>
     [not found]     ` <512EBD01.8010906@linux.vnet.ibm.com>
2013-03-04  2:30       ` Wenchao Xia [this message]
     [not found] ` <1361875228-15769-10-git-send-email-xiawenc@linux.vnet.ibm.com>
     [not found]   ` <874ngxhhfv.fsf@blackfin.pond.sub.org>
     [not found]     ` <20130227162229.GJ2514@dhcp-200-207.str.redhat.com>
     [not found]       ` <513009B9.4090406@linux.vnet.ibm.com>
2013-03-04  3:20         ` [Qemu-devel] [PATCH V7 09/14] block: move bdrv_snapshot_find() to block.c Wenchao Xia
2013-03-04 13:02         ` Stefan Hajnoczi
2013-03-05  7:11           ` Wenchao Xia
2013-03-05  9:21             ` Stefan Hajnoczi
2013-03-05 10:08               ` Kevin Wolf
2013-03-05 10:52                 ` Paolo Bonzini
     [not found] ` <20130228155702.GJ18389@stefanha-thinkpad.redhat.com>
     [not found]   ` <513008B1.8080605@linux.vnet.ibm.com>
2013-03-04 13:10     ` [Qemu-devel] [PATCH V7 00/14] add qmp/hmp interfaces for internal snapshot info Stefan Hajnoczi
2013-03-05  0:43       ` Eric Blake

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=5134075C.7070601@linux.vnet.ibm.com \
    --to=xiawenc@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).