From: Yang Hongyang <yanghy@cn.fujitsu.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>, xen-devel@lists.xen.org
Cc: wei.liu2@citrix.com, ian.campbell@citrix.com,
wency@cn.fujitsu.com, guijianfeng@cn.fujitsu.com,
yunhong.jiang@intel.com, eddie.dong@intel.com,
rshriram@cs.ubc.ca, ian.jackson@eu.citrix.com
Subject: Re: [PATCH v8 --for 4.6 COLO 05/25] tools/libxl: add back channel support to write stream
Date: Thu, 16 Jul 2015 15:21:22 +0800 [thread overview]
Message-ID: <55A75B72.7030106@cn.fujitsu.com> (raw)
In-Reply-To: <55A69771.9030103@citrix.com>
On 07/16/2015 01:25 AM, Andrew Cooper wrote:
> On 15/07/15 10:18, Yang Hongyang wrote:
>> Add back channel support to write stream. If the write stream is
>> a back channel stream, this means the write stream is used by
>> Secondary to send some records back.
>>
>> Signed-off-by: Yang Hongyang <yanghy@cn.fujitsu.com>
>> ---
>> tools/libxl/libxl_dom_save.c | 1 +
>> tools/libxl/libxl_internal.h | 1 +
>> tools/libxl/libxl_stream_write.c | 16 ++++++++++++++++
>> 3 files changed, 18 insertions(+)
>>
>> diff --git a/tools/libxl/libxl_dom_save.c b/tools/libxl/libxl_dom_save.c
>> index 9b7159f..25813ce 100644
>> --- a/tools/libxl/libxl_dom_save.c
>> +++ b/tools/libxl/libxl_dom_save.c
>> @@ -445,6 +445,7 @@ void libxl__domain_save(libxl__egc *egc, libxl__domain_save_state *dss)
>> dss->sws.ao = dss->ao;
>> dss->sws.dss = dss;
>> dss->sws.fd = dss->fd;
>> + dss->sws.back_channel = false;
>> dss->sws.completion_callback = stream_done;
>>
>> libxl__stream_write_start(egc, &dss->sws);
>> diff --git a/tools/libxl/libxl_internal.h b/tools/libxl/libxl_internal.h
>> index 9c81d8d..a83d6a5 100644
>> --- a/tools/libxl/libxl_internal.h
>> +++ b/tools/libxl/libxl_internal.h
>> @@ -2989,6 +2989,7 @@ struct libxl__stream_write_state {
>> libxl__ao *ao;
>> libxl__domain_save_state *dss;
>> int fd;
>> + bool back_channel;
>> void (*completion_callback)(libxl__egc *egc,
>> libxl__stream_write_state *sws,
>> int rc);
>> diff --git a/tools/libxl/libxl_stream_write.c b/tools/libxl/libxl_stream_write.c
>> index 16f667a..df55277 100644
>> --- a/tools/libxl/libxl_stream_write.c
>> +++ b/tools/libxl/libxl_stream_write.c
>> @@ -47,6 +47,13 @@
>> * - Toolstack record
>> * - if (hvm), Qemu record
>> * - Checkpoint end record
>> + *
>> + * For back channel stream:
>> + * - libxl__stream_write_start()
>> + * - Set up the stream to running state
>> + *
>> + * - Add a new API to write the record. When the record is written
>> + * out, call stream->checkpoint_callback() to return.
>> */
>>
>> /* Success/error/cleanup handling. */
>> @@ -178,6 +185,9 @@ void libxl__stream_write_start(libxl__egc *egc,
>>
>> stream->running = true;
>>
>> + if (stream->back_channel)
>> + return;
>> +
>
> Some of the setup below should not be skipped.
>
> While it makes the diff bigger, the end result would be more logical as
>
> dc->ao = ao;
> dc->readfd = -1;
> dc->writefd = stream->fd;
> dc->maxsz = -1;
>
> if (!stream->back_channel) {
> /* Write the stream header. */
> dc->writewhat = "save/migration stream";
> dc->callback = stream_header_done;
>
> rc = ibxl__datacopier_start(dc);
> ....
> }
>
> To split the object setup from the action of sending the stream header,
> which are currently mixed.
>
> What happened to the backchannel negotiation header?
There's no negotiation header currently...If it is a broken back channel,
COLO will fail.
>
> ~Andrew
>
>> dc->ao = ao;
>> dc->readfd = -1;
>> dc->writewhat = "save/migration stream";
>> @@ -207,6 +217,7 @@ void libxl__stream_write_start_checkpoint(libxl__egc *egc,
>> {
>> assert(stream->running);
>> assert(!stream->in_checkpoint);
>> + assert(!stream->back_channel);
>> stream->in_checkpoint = true;
>>
>> write_toolstack_record(egc, stream);
>> @@ -500,6 +511,11 @@ static void stream_done(libxl__egc *egc,
>> assert(stream->running);
>> stream->running = false;
>>
>> + if (stream->back_channel) {
>> + stream->completion_callback(egc, stream, stream->rc);
>> + return;
>> + }
>> +
>> if (stream->emu_carefd)
>> libxl__carefd_close(stream->emu_carefd);
>> free(stream->emu_body);
>
> .
>
--
Thanks,
Yang.
next prev parent reply other threads:[~2015-07-16 7:21 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 9:18 [PATCH v8 --for 4.6 COLO 00/25] COarse-grain LOck-stepping Virtual Machines for Non-stop Service Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 01/25] docs: add colo readme Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 02/25] docs/libxl: Introduce COLO_CONTEXT to support migration v2 colo streams Yang Hongyang
2015-07-15 16:52 ` Andrew Cooper
2015-07-16 6:32 ` Yang Hongyang
2015-07-16 9:45 ` Andrew Cooper
2015-07-16 9:47 ` Andrew Cooper
2015-07-16 10:11 ` Yang Hongyang
2015-07-16 10:20 ` Andrew Cooper
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 03/25] libxc/migration: Specification update for DIRTY_BITMAP records Yang Hongyang
2015-07-15 17:13 ` Andrew Cooper
2015-07-16 7:18 ` Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 04/25] libxc/migration: export read_record for common use Yang Hongyang
2015-07-15 17:14 ` Andrew Cooper
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 05/25] tools/libxl: add back channel support to write stream Yang Hongyang
2015-07-15 17:25 ` Andrew Cooper
2015-07-16 7:21 ` Yang Hongyang [this message]
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 06/25] tools/libxl: write colo_context records into the stream Yang Hongyang
2015-07-15 17:35 ` Andrew Cooper
2015-07-16 7:24 ` Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 07/25] tools/libxl: add back channel support to read stream Yang Hongyang
2015-07-15 17:38 ` Andrew Cooper
2015-07-16 7:25 ` Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 08/25] tools/libxl: handle colo_context records in a libxl migration v2 " Yang Hongyang
2015-07-15 17:44 ` Andrew Cooper
2015-07-16 7:52 ` Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 09/25] tools/libx{l, c}: introduce should_checkpoint callback Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 10/25] tools/libx{l, c}: add postcopy/suspend callback to restore side Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 11/25] secondary vm suspend/resume/checkpoint code Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 12/25] primary " Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 13/25] libxc/restore: support COLO restore Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 14/25] libxc/restore: send dirty bitmap to primary when checkpoint under colo Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 15/25] send store mfn and console mfn to xl before resuming secondary vm Yang Hongyang
2015-07-15 18:15 ` Andrew Cooper
2015-07-16 7:56 ` Yang Hongyang
2015-07-16 9:49 ` Andrew Cooper
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 16/25] libxc/save: support COLO save Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 17/25] implement the cmdline for COLO Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 18/25] Support colo mode for qemu disk Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 19/25] COLO: use qemu block replication Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 20/25] COLO proxy: implement setup/teardown of COLO proxy module Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 21/25] COLO proxy: preresume, postresume and checkpoint Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 22/25] COLO nic: implement COLO nic subkind Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 23/25] setup and control colo proxy on primary side Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 24/25] setup and control colo proxy on secondary side Yang Hongyang
2015-07-15 9:18 ` [PATCH v8 --for 4.6 COLO 25/25] cmdline switches and config vars to control colo-proxy Yang Hongyang
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=55A75B72.7030106@cn.fujitsu.com \
--to=yanghy@cn.fujitsu.com \
--cc=andrew.cooper3@citrix.com \
--cc=eddie.dong@intel.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=rshriram@cs.ubc.ca \
--cc=wei.liu2@citrix.com \
--cc=wency@cn.fujitsu.com \
--cc=xen-devel@lists.xen.org \
--cc=yunhong.jiang@intel.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.