qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Changlong Xie <xiecl.fnst@cn.fujitsu.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu devel <qemu-devel@nongnu.org>, Fam Zheng <famz@redhat.com>,
	Max Reitz <mreitz@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Kevin Wolf <kwolf@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Dong Eddie <eddie.dong@intel.com>,
	Jiang Yunhong <yunhong.jiang@intel.com>,
	Wen Congyang <wency@cn.fujitsu.com>,
	qemu block <qemu-block@nongnu.org>,
	"Michael R. Hines" <mrhines@linux.vnet.ibm.com>,
	Eric Blake <eblake@redhat.com>,
	zhanghailiang <zhang.zhanghailiang@huawei.com>,
	Gonglei <arei.gonglei@huawei.com>
Subject: Re: [Qemu-devel] [PATCH v17 6/8] Introduce new APIs to do replication operation
Date: Thu, 14 Apr 2016 09:47:19 +0800	[thread overview]
Message-ID: <570EF6A7.4010806@cn.fujitsu.com> (raw)
In-Reply-To: <20160413124757.GC9272@stefanha-x1.localdomain>

On 04/13/2016 08:47 PM, Stefan Hajnoczi wrote:
> On Mon, Apr 11, 2016 at 04:22:57PM +0800, Changlong Xie wrote:
>> +/*
>> + * The caller of the function MUST make sure vm stopped
>> + */
>> +void replication_start_all(ReplicationMode mode, Error **errp)
>> +{
>> +    ReplicationState *rs, *next;
>> +
>> +    QLIST_FOREACH_SAFE(rs, &replication_states, node, next) {
>> +        if (rs->ops && rs->ops->start) {
>> +            rs->ops->start(rs, mode, errp);
>> +        }
>> +        if (errp && *errp) {
>> +            return;
>> +        }
>
> This function returns immediately on error if the caller provided errp.
> It continues if the caller did not provide errp.
>
> I'm not sure if you wanted this difference in behavior.
>
> The following always returns immediately on error, even when the caller
> did not provide errp:
>

I just notice that, if errp == NULL and error happens in 
rs->ops->{start,...}, we could never detect it. I'll check all 
replication callbacks carefully

Thanks
	-Xie
> void replication_start_all(ReplicationMode mode, Error **errp)
> {
>      ReplicationState *rs, *next;
>      Error *local_err = NULL;
>
>      QLIST_FOREACH_SAFE(rs, &replication_states, node, next) {
>          if (rs->ops && rs->ops->start) {
>              rs->ops->start(rs, mode, &local_err);
>          }
>          if (local_err) {
> 	    error_propagate(errp, local_err);
>              return;
>          }
>> +/**
>> + * SECTION:replication.h
>> + * @title:Base Replication System
>> + * @short_description: interfaces for handle replication
>> + *
>> + * The Replication Model provides a framework for handle Replication
>
> s/handle/handling/
>

  reply	other threads:[~2016-04-14  1:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11  8:22 [Qemu-devel] [PATCH v17 0/8] Block replication for continuous checkpoints Changlong Xie
2016-04-11  8:22 ` [Qemu-devel] [PATCH v17 1/8] unblock backup operations in backing file Changlong Xie
2016-04-11  8:22 ` [Qemu-devel] [PATCH v17 2/8] Backup: clear all bitmap when doing block checkpoint Changlong Xie
2016-04-11  8:22 ` [Qemu-devel] [PATCH v17 3/8] Link backup into block core Changlong Xie
2016-04-11  8:22 ` [Qemu-devel] [PATCH v17 4/8] docs: block replication's description Changlong Xie
2016-04-11  8:22 ` [Qemu-devel] [PATCH v17 5/8] auto complete active commit Changlong Xie
2016-04-11  8:22 ` [Qemu-devel] [PATCH v17 6/8] Introduce new APIs to do replication operation Changlong Xie
2016-04-13 12:47   ` Stefan Hajnoczi
2016-04-14  1:47     ` Changlong Xie [this message]
2016-04-11  8:22 ` [Qemu-devel] [PATCH v17 7/8] Implement new driver for block replication Changlong Xie
2016-04-13 13:02   ` Stefan Hajnoczi
2016-04-14  3:46     ` Changlong Xie
2016-04-11  8:22 ` [Qemu-devel] [PATCH v17 8/8] support replication driver in blockdev-add Changlong Xie

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=570EF6A7.4010806@cn.fujitsu.com \
    --to=xiecl.fnst@cn.fujitsu.com \
    --cc=arei.gonglei@huawei.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=eddie.dong@intel.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=mrhines@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=wency@cn.fujitsu.com \
    --cc=yunhong.jiang@intel.com \
    --cc=zhang.zhanghailiang@huawei.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).