From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Wen Congyang <wency@cn.fujitsu.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: Wed, 30 Dec 2015 10:47:22 +0000 [thread overview]
Message-ID: <5683B63A.3080601@citrix.com> (raw)
In-Reply-To: <1451439588-25310-3-git-send-email-wency@cn.fujitsu.com>
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?
> 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-30 10:47 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 [this message]
2015-12-31 1:00 ` Wen Congyang
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=5683B63A.3080601@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=hongyang.yang@easystack.cn \
--cc=rshriram@cs.ubc.ca \
--cc=wency@cn.fujitsu.com \
--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 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).