From: Wen Congyang <wency@cn.fujitsu.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
xen devel <xen-devel@lists.xen.org>
Cc: Shriram Rajagopalan <rshriram@cs.ubc.ca>,
Changlong Xie <xiecl.fnst@cn.fujitsu.com>,
Yang Hongyang <hongyang.yang@easystack.cn>
Subject: Re: [PATCH 2/5] remus: don't write xenstore data if it fails
Date: Thu, 31 Dec 2015 09:00:54 +0800 [thread overview]
Message-ID: <56847E46.1000002@cn.fujitsu.com> (raw)
In-Reply-To: <5683B63A.3080601@citrix.com>
On 12/30/2015 06:47 PM, Andrew Cooper wrote:
> On 30/12/2015 01:39, Wen Congyang wrote:
>
> If what fails?
>
> Given the content of this patch in the context of the previous one, I presume you are wishing to avoid re-sending the emulator state after libxl__xc_domain_save_done() completes, but under what circumstances will this occur?
For example: if the secondary host is down, and we fail to send the data to
the secondary host. xc_domain_save() returns 0. So in the function
libxl__xc_domain_save_done(), rc is 0(the helper program exits normally),
and retval is 0(it is xc_domain_save()'s return value).
Thanks
Wen Congyang
>
>> Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
>> ---
>> tools/libxl/libxl_stream_write.c | 8 ++++++--
>> 1 file changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/tools/libxl/libxl_stream_write.c b/tools/libxl/libxl_stream_write.c
>> index 80d9208..ee9c53a 100644
>> --- a/tools/libxl/libxl_stream_write.c
>> +++ b/tools/libxl/libxl_stream_write.c
>> @@ -354,8 +354,12 @@ void libxl__xc_domain_save_done(libxl__egc *egc, void *dss_void,
>> * alive, and check_all_finished() may have torn it down around us.
>> * If the stream is not still alive, we must not continue any work.
>> */
>> - if (libxl__stream_write_inuse(stream))
>> - write_emulator_xenstore_record(egc, stream);
>> + if (libxl__stream_write_inuse(stream)) {
>> + if (dss->remus)
>> + stream_complete(egc, stream, 0);
>> + else
>> + write_emulator_xenstore_record(egc, stream);
>> + }
>> }
>> static void write_emulator_xenstore_record(libxl__egc *egc,
>
>
>
> .
>
next prev parent reply other threads:[~2015-12-31 1:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 1:39 [PATCH 0/5] migration/remus: bug fix and cleanup Wen Congyang
2015-12-30 1:39 ` [PATCH 1/5] remus: don't call stream_continue() when doing failover Wen Congyang
2015-12-30 10:43 ` Andrew Cooper
2015-12-30 1:39 ` [PATCH 2/5] remus: don't write xenstore data if it fails Wen Congyang
2015-12-30 10:47 ` Andrew Cooper
2015-12-31 1:00 ` Wen Congyang [this message]
2015-12-30 1:39 ` [PATCH 3/5] tools/libxc: don't send end record if remus fails Wen Congyang
2015-12-30 11:11 ` Andrew Cooper
2015-12-31 0:49 ` Wen Congyang
2015-12-30 1:39 ` [PATCH 4/5] tools/libxl: remove unused function libxl__domain_save_device_model() Wen Congyang
2015-12-30 1:39 ` [PATCH 5/5] Allow all user to create a file under the directory /var/lib/xen Wen Congyang
2015-12-30 4:11 ` Doug Goldstein
2015-12-30 5:25 ` Wen Congyang
2015-12-30 11:00 ` Andrew Cooper
2016-01-25 20:36 ` Konrad Rzeszutek Wilk
2016-01-26 0:00 ` Andrew Cooper
2016-01-26 9:30 ` Ian Campbell
2016-01-26 17:15 ` Stefano Stabellini
2016-01-27 9:48 ` Ian Campbell
2015-12-30 10:38 ` [PATCH 0/5] migration/remus: bug fix and cleanup Andrew Cooper
2015-12-31 0:48 ` Wen Congyang
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=56847E46.1000002@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=andrew.cooper3@citrix.com \
--cc=hongyang.yang@easystack.cn \
--cc=rshriram@cs.ubc.ca \
--cc=xen-devel@lists.xen.org \
--cc=xiecl.fnst@cn.fujitsu.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 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.