From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH] QMP: add snapshot_blkdev_sync command
Date: Thu, 10 Mar 2011 10:10:36 +0100 [thread overview]
Message-ID: <4D78958C.3030604@redhat.com> (raw)
In-Reply-To: <4D77B2FD.3050304@codemonkey.ws>
On 03/09/11 18:03, Anthony Liguori wrote:
> On 03/09/2011 10:01 AM, Kevin Wolf wrote:
>>> I'm not sure blkdev is the right prefix. Kevin, what are your thoughts
>>> here? Does 'blkdev' make sense for any command operating on a block
>>> device (that is, a qdev device that happens to have a block drive, not
>>> the same thing as -blockdev that we've discussed in the past).
>> Doesn't this command work on a -blockdev style thing, i.e.
>> BlockDriverState or DriveInfo? I don't think we have any commands that
>> refer to qdev devices that happen to be block devices. You could
>> probably argue that some of them should...
>
> 'device' is a device name though, right? Or is it a name associated
> with a BlockDriverState that currently happens to be a qdev name?
It is a device in the sense of what you get from 'info block' in the
human monitor.
> Would I be able to eventually pass a qdev path here?
>
> If the answer is that this is a bdrv_name, then should we at least use
> blockdev instead of blkdev?
I used blkdev in the human monitor command to reduce the length of the
command name.
Anyway, if you can decide what you want to call the command, I'll rename
it accordingly.
Cheers,
Jes
next prev parent reply other threads:[~2011-03-10 9:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 15:37 [Qemu-devel] [PATCH] QMP: add snapshot_blkdev_sync command Jes.Sorensen
2011-03-09 15:46 ` Anthony Liguori
2011-03-09 16:01 ` Kevin Wolf
2011-03-09 17:03 ` Anthony Liguori
2011-03-10 9:10 ` Jes Sorensen [this message]
2011-03-10 9:21 ` Kevin Wolf
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=4D78958C.3030604@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.