qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, benoit.canet@gmail.com,
	"Benoît Canet" <benoit@irqsave.net>,
	qemu-devel@nongnu.org, pbonzini@redhat.com,
	stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH V5 2/4] block: Use bdrv_get_backing_file_depth()
Date: Mon, 30 Jul 2012 14:00:28 -0300	[thread overview]
Message-ID: <20120730140028.68aaabc1@doriath.home> (raw)
In-Reply-To: <5016BAF1.8020302@redhat.com>

On Mon, 30 Jul 2012 10:48:49 -0600
Eric Blake <eblake@redhat.com> wrote:

> On 07/30/2012 10:32 AM, Luiz Capitulino wrote:
> > On Thu, 26 Jul 2012 15:18:19 +0200
> > benoit.canet@gmail.com wrote:
> > 
> >> From: Benoît Canet <benoit@irqsave.net>
> >>
> >> Use the dedicated counting function in qmp_query_block in order to
> >> propagate the backing file depth to HMP.
> >>
> >> Signed-off-by: Benoit Canet <benoit@irqsave.net>
> 
> >> +++ b/qapi-schema.json
> >> @@ -398,6 +398,8 @@
> >>  #
> >>  # @backing_file: #optional the name of the backing file (for copy-on-write)
> >>  #
> >> +# @backing_file_depth: number of files in the backing file chain (since: 1.2)
> >> +#
> >>  # @encrypted: true if the backing device is encrypted
> >>  #
> >>  # @bps: total throughput limit in bytes per second is specified
> >> @@ -418,9 +420,10 @@
> >>  ##
> >>  { 'type': 'BlockDeviceInfo',
> >>    'data': { 'file': 'str', 'ro': 'bool', 'drv': 'str',
> >> -            '*backing_file': 'str', 'encrypted': 'bool',
> >> -            'bps': 'int', 'bps_rd': 'int', 'bps_wr': 'int',
> >> -            'iops': 'int', 'iops_rd': 'int', 'iops_wr': 'int'} }
> >> +            '*backing_file': 'str', 'backing-file-depth': 'int',
> > 
> > Should use underscores, ie. should be backing_file_depth.
> 
> Really?  I thought we _want_ new interfaces to use '-', not '_', in QMP.

The problem is mixing them. BlockDeviceInfo already uses "_", and it's
not only for backing_file.

For new commands or existing commands that don't use "_", we certainly should
use "-", but mixing them for the same command is probably a bad thing.

>  For 'backing_file', we are stuck due to back-compat (unless Anthony's
> proposed patch to parse names case-insensitively with '-' and '_' folded
> together is taken),

We can't take Anthony's patch for what we emit. We could use it for input,
but I don't think it's worth it.

> but for the new field, we have no back-compat
> constraints, and I would prefer backing-file-depth.

It's like not I can't be convinced, but I think we shouldn't mix "-" and
"_" for the same command.

> 
> At any rate, you definitely need to make sure you agree between the docs
> above and the JSON statement below (as written, you have both spellings
> in the same patch).
> 

  reply	other threads:[~2012-07-30 17:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 13:18 [Qemu-devel] [PATCH V5 0/4] Show backing file depth in HMP and QMP benoit.canet
2012-07-26 13:18 ` [Qemu-devel] [PATCH V5 1/4] block: create bdrv_get_backing_file_depth() benoit.canet
2012-07-26 13:18 ` [Qemu-devel] [PATCH V5 2/4] block: Use bdrv_get_backing_file_depth() benoit.canet
2012-07-30 16:32   ` Luiz Capitulino
2012-07-30 16:48     ` Eric Blake
2012-07-30 17:00       ` Luiz Capitulino [this message]
2012-07-26 13:18 ` [Qemu-devel] [PATCH V5 3/4] qmp: Add backing-file-depth to qmp-commands.hx benoit.canet
2012-07-26 13:18 ` [Qemu-devel] [PATCH V5 4/4] hmp: show the backing file depth benoit.canet
2012-07-26 13:39 ` [Qemu-devel] [PATCH V5 0/4] Show backing file depth in HMP and QMP 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=20120730140028.68aaabc1@doriath.home \
    --to=lcapitulino@redhat.com \
    --cc=benoit.canet@gmail.com \
    --cc=benoit@irqsave.net \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.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).