From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, pbonzini@redhat.com, stefanha@gmail.com,
qemu-devel@nongnu.org, dietmar@proxmox.com
Subject: Re: [Qemu-devel] [PATCH V4 5/5] block: make all steps in qmp_transaction() as callback
Date: Mon, 06 May 2013 10:00:45 +0800 [thread overview]
Message-ID: <51870ECD.6090304@linux.vnet.ibm.com> (raw)
In-Reply-To: <5183CDCE.70005@redhat.com>
于 2013-5-3 22:46, Eric Blake 写道:
> On 05/01/2013 08:26 PM, Wenchao Xia wrote:
>> Make it easier to add other operations to qmp_transaction() by using
>> callbacks, with external snapshots serving as an example implementation
>> of the callbacks.
>>
>> Signed-off-by: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
>> ---
>> blockdev.c | 92 ++++++++++++++++++++++++++++++++++++++++++++++-------------
>> 1 files changed, 71 insertions(+), 21 deletions(-)
>>
>
>> +/*
>> + * This structure must be arranged as first member in parent type, assuming
>
> To me, "parent type" seems like the wrong relationship - in C++, the
> parent type is the smaller type, and the child type is the larger type
> that includes the parent type as its first member. That is,
> BlkTransationStates IS the parent type, and the comment would read
> better as "first member in child type".
>
>> + * that compiler will also arrange it to the same address with parent instance.
>> + * Later it will be used in free().
>> + */
>> +struct BlkTransactionStates {
>> + BlockdevAction *action;
>> + const BdrvActionOps *ops;
>> + QSIMPLEQ_ENTRY(BlkTransactionStates) entry;
>> +};
>>
>
>>
>> /* Now we are going to do the actual pivot. Everything up to this point
>> * is reversible, but we are committed at this point */
>
> Is this comment still correct, now that things are extensible, or should
> you s/pivot/commit/?
>
> If you do respin, I agree that s/rollback/abort/ might be a nicer name
> for that particular callback. But I'm also quite okay with using the
> patch as-is without a respin (while I pointed out two possible comment
> wording changes, they don't make or break the patch for me).
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
I'll respin to fix comments and use "abort" as v5, thanks for your
reviewing!
--
Best Regards
Wenchao Xia
next prev parent reply other threads:[~2013-05-06 2:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 2:26 [Qemu-devel] [PATCH V4 0/5] block: make qmp_transaction extendable Wenchao Xia
2013-05-02 2:26 ` [Qemu-devel] [PATCH V4 1/5] block: package preparation code in qmp_transaction() Wenchao Xia
2013-05-03 14:18 ` Eric Blake
2013-05-02 2:26 ` [Qemu-devel] [PATCH V4 2/5] block: move input parsing " Wenchao Xia
2013-05-02 2:26 ` [Qemu-devel] [PATCH V4 3/5] block: package committing " Wenchao Xia
2013-05-03 14:21 ` Eric Blake
2013-05-02 2:26 ` [Qemu-devel] [PATCH V4 4/5] block: package rollback " Wenchao Xia
2013-05-03 14:40 ` Eric Blake
2013-05-02 2:26 ` [Qemu-devel] [PATCH V4 5/5] block: make all steps in qmp_transaction() as callback Wenchao Xia
2013-05-03 14:46 ` Eric Blake
2013-05-06 2:00 ` Wenchao Xia [this message]
2013-05-03 8:46 ` [Qemu-devel] [PATCH V4 0/5] block: make qmp_transaction extendable Kevin Wolf
2013-05-03 11:17 ` Stefan Hajnoczi
2013-05-06 15:56 ` Luiz Capitulino
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=51870ECD.6090304@linux.vnet.ibm.com \
--to=xiawenc@linux.vnet.ibm.com \
--cc=dietmar@proxmox.com \
--cc=eblake@redhat.com \
--cc=kwolf@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).