From: Kevin Wolf <kwolf@redhat.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, dietmar@proxmox.com,
stefanha@gmail.com
Subject: Re: [Qemu-devel] [PATCH V5 0/5] block: make qmp_transaction extendable
Date: Wed, 8 May 2013 13:21:04 +0200 [thread overview]
Message-ID: <20130508112104.GF3093@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1368008716-9632-1-git-send-email-xiawenc@linux.vnet.ibm.com>
Am 08.05.2013 um 12:25 hat Wenchao Xia geschrieben:
> This serial will package backing chain snapshot code as one case, to make it
> possible adding more operations later.
>
> v2:
> Address Kevin's comments:
> Use the same prototype prepare, commit, rollback model in original code,
> commit should never fail.
>
> v3:
> Address Stefan's comments:
> 3/5, 4/5: remove *action parameter since later only BlkTransactionStates* is
> needed.
> 5/5: embbed BlkTransactionStates in ExternalSnapshotStates, *opaque is
> removed, related call back function format change for external snapshot.
> Address Kevin's comments:
> removed all indention in commit message.
> 1/5: return void for prepare() function, *errp plays the role as error
> checker.
> 5/5: mark *commit callback must exist, *rollback callback can be NULL. Align
> "callback =" in "const BdrvActionOps external_snapshot_ops" to the same colum.
> Address Eric's comments:
> 1/5: better commit message.
> 5/5: better commit message and comments in code that only one of rollback()
> or commit() will be called.
>
> v4:
> 5/5: document clean() callback will always be called if it present, declare
> static for global variable "actions", use array plus .instance_size to remove
> "switch" checking code according to caller input.
>
> v5:
> better commit message and comments, switch callback function name "rollback"
> to "abort".
>
> Wenchao Xia (5):
> 1 block: package preparation code in qmp_transaction()
> 2 block: move input parsing code in qmp_transaction()
> 3 block: package committing code in qmp_transaction()
> 4 block: package rollback code in qmp_transaction()
> 5 block: make all steps in qmp_transaction() as callback
>
> blockdev.c | 266 ++++++++++++++++++++++++++++++++++++++----------------------
> 1 files changed, 169 insertions(+), 97 deletions(-)
Thanks, applied all to block-next for 1.6.
Kevin
next prev parent reply other threads:[~2013-05-08 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 10:25 [Qemu-devel] [PATCH V5 0/5] block: make qmp_transaction extendable Wenchao Xia
2013-05-08 10:25 ` [Qemu-devel] [PATCH V5 1/5] block: package preparation code in qmp_transaction() Wenchao Xia
2013-05-08 10:25 ` [Qemu-devel] [PATCH V5 2/5] block: move input parsing " Wenchao Xia
2013-05-08 10:25 ` [Qemu-devel] [PATCH V5 3/5] block: package committing " Wenchao Xia
2013-05-08 10:25 ` [Qemu-devel] [PATCH V5 4/5] block: package rollback " Wenchao Xia
2013-05-08 10:25 ` [Qemu-devel] [PATCH V5 5/5] block: make all steps in qmp_transaction() as callback Wenchao Xia
2013-05-08 11:21 ` Kevin Wolf [this message]
2013-05-14 6:51 ` [Qemu-devel] [PATCH V5 0/5] block: make qmp_transaction extendable Wenchao Xia
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=20130508112104.GF3093@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=dietmar@proxmox.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=xiawenc@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).