From: zhanghailiang <zhang.zhanghailiang@huawei.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: lizhijian@cn.fujitsu.com, quintela@redhat.com,
yunhong.jiang@intel.com, eddie.dong@intel.com,
peter.huangpeng@huawei.com, qemu-devel@nongnu.org,
arei.gonglei@huawei.com, stefanha@redhat.com,
amit.shah@redhat.com, yanghy@cn.fujitsu.com
Subject: Re: [Qemu-devel] [PATCH COLO-Frame v9 06/32] migration: Integrate COLO checkpoint process into loadvm
Date: Tue, 20 Oct 2015 16:04:33 +0800 [thread overview]
Message-ID: <5625F591.5050601@huawei.com> (raw)
In-Reply-To: <20151019091746.GA2462@work-vm>
On 2015/10/19 17:17, Dr. David Alan Gilbert wrote:
> * zhanghailiang (zhang.zhanghailiang@huawei.com) wrote:
>> Switch from normal migration loadvm process into COLO checkpoint process if
>> COLO mode is enabled.
>> We add three new members to struct MigrationIncomingState, 'have_colo_incoming_thread'
>> and 'colo_incoming_thread' record the colo related threads for secondary VM,
>> 'migration_incoming_co' records the original migration incoming coroutine.
>>
>> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
>> Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
>> Signed-off-by: Yang Hongyang <yanghy@cn.fujitsu.com>
>
> Mostly OK, some mostly minor comments, and one question below:
>
>> ---
>> include/migration/colo.h | 7 +++++++
>> include/migration/migration.h | 7 +++++++
>> migration/colo-comm.c | 10 ++++++++++
>> migration/colo.c | 22 ++++++++++++++++++++++
>> migration/migration.c | 33 +++++++++++++++++++++++----------
>> stubs/migration-colo.c | 10 ++++++++++
>> trace-events | 1 +
>> 7 files changed, 80 insertions(+), 10 deletions(-)
>>
>> diff --git a/include/migration/colo.h b/include/migration/colo.h
>> index dface19..58849f7 100644
>> --- a/include/migration/colo.h
>> +++ b/include/migration/colo.h
>> @@ -15,6 +15,8 @@
>>
>> #include "qemu-common.h"
>> #include "migration/migration.h"
>> +#include "block/coroutine.h"
>> +#include "qemu/thread.h"
>>
>> bool colo_supported(void);
>> void colo_info_mig_init(void);
>> @@ -22,4 +24,9 @@ void colo_info_mig_init(void);
>> void colo_init_checkpointer(MigrationState *s);
>> bool migration_in_colo_state(void);
>>
>> +/* loadvm */
>> +bool migration_incoming_enable_colo(void);
>> +void migration_incoming_exit_colo(void);
>> +void *colo_process_incoming_thread(void *opaque);
>> +bool migration_incoming_in_colo_state(void);
>> #endif
>> diff --git a/include/migration/migration.h b/include/migration/migration.h
>> index a62068f..9cdd6b6 100644
>> --- a/include/migration/migration.h
>> +++ b/include/migration/migration.h
>> @@ -22,6 +22,7 @@
>> #include "migration/vmstate.h"
>> #include "qapi-types.h"
>> #include "exec/cpu-common.h"
>> +#include "block/coroutine.h"
>>
>> #define QEMU_VM_FILE_MAGIC 0x5145564d
>> #define QEMU_VM_FILE_VERSION_COMPAT 0x00000002
>> @@ -51,6 +52,12 @@ struct MigrationIncomingState {
>> QEMUFile *file;
>>
>> int state;
>> +
>> + bool have_colo_incoming_thread;
>> + QemuThread colo_incoming_thread;
>> + /* The coroutine we should enter (back) after failover */
>> + Coroutine *migration_incoming_co;
>> +
>> /* See savevm.c */
>> LoadStateEntry_Head loadvm_handlers;
>> };
>> diff --git a/migration/colo-comm.c b/migration/colo-comm.c
>> index 4330bd8..0808d6c 100644
>> --- a/migration/colo-comm.c
>> +++ b/migration/colo-comm.c
>> @@ -52,3 +52,13 @@ void colo_info_mig_init(void)
>> {
>> vmstate_register(NULL, 0, &colo_state, &colo_info);
>> }
>> +
>> +bool migration_incoming_enable_colo(void)
>> +{
>> + return colo_info.colo_requested;
>> +}
>> +
>> +void migration_incoming_exit_colo(void)
>> +{
>> + colo_info.colo_requested = 0;
>> +}
>> diff --git a/migration/colo.c b/migration/colo.c
>> index 97e64a3..a341eee 100644
>> --- a/migration/colo.c
>> +++ b/migration/colo.c
>> @@ -13,6 +13,7 @@
>> #include "sysemu/sysemu.h"
>> #include "migration/colo.h"
>> #include "trace.h"
>> +#include "qemu/error-report.h"
>>
>> static QEMUBH *colo_bh;
>>
>> @@ -28,6 +29,13 @@ bool migration_in_colo_state(void)
>> return (s->state == MIGRATION_STATUS_COLO);
>> }
>>
>> +bool migration_incoming_in_colo_state(void)
>> +{
>> + MigrationIncomingState *mis = migration_incoming_get_current();
>> +
>> + return (mis && (mis->state == MIGRATION_STATUS_COLO));
>
> Can remove outer brackets.
>
OK.
>> +}
>> +
>> static void *colo_thread(void *opaque)
>> {
>> MigrationState *s = opaque;
>> @@ -74,3 +82,17 @@ void colo_init_checkpointer(MigrationState *s)
>> colo_bh = qemu_bh_new(colo_start_checkpointer, s);
>> qemu_bh_schedule(colo_bh);
>> }
>> +
>> +void *colo_process_incoming_thread(void *opaque)
>> +{
>> + MigrationIncomingState *mis = opaque;
>> +
>> + migrate_set_state(&mis->state, MIGRATION_STATUS_ACTIVE,
>> + MIGRATION_STATUS_COLO);
>> +
>> + /* TODO: COLO checkpoint restore loop */
>> +
>> + migration_incoming_exit_colo();
>> +
>> + return NULL;
>> +}
>> diff --git a/migration/migration.c b/migration/migration.c
>> index bee61aa..241689f 100644
>> --- a/migration/migration.c
>> +++ b/migration/migration.c
>> @@ -280,7 +280,28 @@ static void process_incoming_migration_co(void *opaque)
>> MIGRATION_STATUS_ACTIVE);
>> ret = qemu_loadvm_state(f);
>>
>> - qemu_fclose(f);
>> + if (!ret) {
>> + /* Make sure all file formats flush their mutable metadata */
>> + bdrv_invalidate_cache_all(&local_err);
>> + if (local_err) {
>> + error_report_err(local_err);
>> + migrate_decompress_threads_join();
>> + exit(EXIT_FAILURE);
>> + }
>> + }
>> + /* we get colo info, and know if we are in colo mode */
>> + if (!ret && migration_incoming_enable_colo()) {
>> + mis->migration_incoming_co = qemu_coroutine_self();
>> + qemu_thread_create(&mis->colo_incoming_thread, "colo incoming",
>> + colo_process_incoming_thread, mis, QEMU_THREAD_JOINABLE);
>> + mis->have_colo_incoming_thread = true;
>> + qemu_coroutine_yield();
>> +
>> + /* Wait checkpoint incoming thread exit before free resource */
>> + qemu_thread_join(&mis->colo_incoming_thread);
>> + } else {
>> + qemu_fclose(f);
>> + }
>
> Why is that qemu_fclose(f) in the else ? If you do colo, and do the colo
> thread, when the incoming colo thread exits, don't we return here - and if
> we return here then don't we want to close f? (I guess this only happens
> on a failover to secondary?)
>
Er,it is a bug, we closed it in colo incoming thread before in old version, but after
several version, we lost it.
I will fix it in next version.
>> free_xbzrle_decoded_buf();
>> migration_incoming_state_destroy();
>>
>> @@ -295,18 +316,9 @@ static void process_incoming_migration_co(void *opaque)
>> MIGRATION_STATUS_COMPLETED);
>> qemu_announce_self();
>>
>> - /* Make sure all file formats flush their mutable metadata */
>> - bdrv_invalidate_cache_all(&local_err);
>> - if (local_err) {
>> - error_report_err(local_err);
>> - migrate_decompress_threads_join();
>> - exit(EXIT_FAILURE);
>> - }
>> -
>> /* If global state section was not received or we are in running
>> state, we need to obey autostart. Any other state is set with
>> runstate_set. */
>> -
>> if (!global_state_received() ||
>> global_state_get_runstate() == RUN_STATE_RUNNING) {
>> if (autostart) {
>> @@ -740,6 +752,7 @@ void qmp_migrate(const char *uri, bool has_blk, bool blk,
>> error_setg(errp, QERR_MIGRATION_ACTIVE);
>> return;
>> }
>> +
>> if (runstate_check(RUN_STATE_INMIGRATE)) {
>> error_setg(errp, "Guest is waiting for an incoming migration");
>> return;
>> diff --git a/stubs/migration-colo.c b/stubs/migration-colo.c
>> index 51b8f66..c49ee1a 100644
>> --- a/stubs/migration-colo.c
>> +++ b/stubs/migration-colo.c
>> @@ -22,6 +22,16 @@ bool migration_in_colo_state(void)
>> return false;
>> }
>>
>> +bool migration_incoming_in_colo_state(void)
>> +{
>> + return false;
>> +}
>> +
>> void colo_init_checkpointer(MigrationState *s)
>> {
>> }
>> +
>> +void *colo_process_incoming_thread(void *opaque)
>> +{
>> + return NULL;
>> +}
>> diff --git a/trace-events b/trace-events
>> index 487d1c7..352e9c3 100644
>> --- a/trace-events
>> +++ b/trace-events
>> @@ -1474,6 +1474,7 @@ rdma_start_outgoing_migration_after_rdma_source_init(void) ""
>>
>> # migration/colo.c
>> colo_vm_state_change(const char *old, const char *new) "Change '%s' => '%s'"
>> +colo_receive_message(const char *msg) "Receive '%s'"
>
> Should be in a different patch?
>
This is a residual, i have removed it.
Thanks,
zhanghailiang
> Dave
>
>> # kvm-all.c
>> kvm_ioctl(int type, void *arg) "type 0x%x, arg %p"
>> --
>> 1.8.3.1
>>
>>
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>
> .
>
next prev parent reply other threads:[~2015-10-20 8:11 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 8:22 [Qemu-devel] [PATCH COLO-Frame v9 00/32] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service (FT) zhanghailiang
2015-09-02 8:22 ` [Qemu-devel] [PATCH COLO-Frame v9 01/32] configure: Add parameter for configure to enable/disable COLO support zhanghailiang
2015-10-02 15:10 ` Dr. David Alan Gilbert
2015-09-02 8:22 ` [Qemu-devel] [PATCH COLO-Frame v9 02/32] migration: Introduce capability 'colo' to migration zhanghailiang
2015-10-02 16:02 ` Eric Blake
2015-10-08 6:34 ` zhanghailiang
2015-09-02 8:22 ` [Qemu-devel] [PATCH COLO-Frame v9 03/32] COLO: migrate colo related info to slave zhanghailiang
2015-10-02 18:45 ` Dr. David Alan Gilbert
2015-10-08 6:48 ` zhanghailiang
2015-09-02 8:22 ` [Qemu-devel] [PATCH COLO-Frame v9 04/32] migration: Add state records for migration incoming zhanghailiang
2015-10-09 16:18 ` Dr. David Alan Gilbert
2015-10-10 7:07 ` zhanghailiang
2015-10-16 11:14 ` Dr. David Alan Gilbert
2015-09-02 8:22 ` [Qemu-devel] [PATCH COLO-Frame v9 05/32] migration: Integrate COLO checkpoint process into migration zhanghailiang
2015-10-09 16:53 ` Dr. David Alan Gilbert
2015-10-10 6:25 ` zhanghailiang
2015-09-02 8:22 ` [Qemu-devel] [PATCH COLO-Frame v9 06/32] migration: Integrate COLO checkpoint process into loadvm zhanghailiang
2015-10-19 9:17 ` Dr. David Alan Gilbert
2015-10-20 8:04 ` zhanghailiang [this message]
2015-09-02 8:22 ` [Qemu-devel] [PATCH COLO-Frame v9 07/32] migration: Rename the'file' member of MigrationState and MigrationIncomingState zhanghailiang
2015-09-02 8:22 ` [Qemu-devel] [PATCH COLO-Frame v9 08/32] COLO/migration: establish a new communication path from destination to source zhanghailiang
2015-10-19 9:54 ` Dr. David Alan Gilbert
2015-10-20 8:30 ` zhanghailiang
2015-10-20 19:32 ` Dr. David Alan Gilbert
2015-10-21 8:33 ` zhanghailiang
2015-09-02 8:22 ` [Qemu-devel] [PATCH COLO-Frame v9 09/32] COLO: Implement colo checkpoint protocol zhanghailiang
2015-10-21 12:17 ` Eric Blake
2015-10-22 7:13 ` zhanghailiang
2015-09-02 8:22 ` [Qemu-devel] [PATCH COLO-Frame v9 10/32] COLO: Add a new RunState RUN_STATE_COLO zhanghailiang
2015-10-21 12:18 ` Eric Blake
2015-10-22 6:58 ` zhanghailiang
2015-09-02 8:22 ` [Qemu-devel] [PATCH COLO-Frame v9 11/32] QEMUSizedBuffer: Introduce two help functions for qsb zhanghailiang
2015-09-02 8:22 ` [Qemu-devel] [PATCH COLO-Frame v9 12/32] COLO: Save PVM state to secondary side when do checkpoint zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 13/32] COLO: Load PVM's dirty pages into SVM's RAM cache temporarily zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 14/32] COLO: Load VMState into qsb before restore it zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 15/32] COLO: Flush PVM's cached RAM into SVM's memory zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 16/32] COLO: synchronize PVM's state to SVM periodically zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 17/32] COLO failover: Introduce a new command to trigger a failover zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 18/32] COLO failover: Introduce state to record failover process zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 19/32] COLO: Implement failover work for Primary VM zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 20/32] COLO: Implement failover work for Secondary VM zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 21/32] COLO: implement default failover treatment zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 22/32] qmp event: Add event notification for COLO error zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 23/32] COLO failover: Shutdown related socket fd when do failover zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 24/32] COLO failover: Don't do failover during loading VM's state zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 25/32] COLO: Control the checkpoint delay time by migrate-set-parameters command zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 26/32] COLO: Implement shutdown checkpoint zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 27/32] COLO: Update the global runstate after going into colo state zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 28/32] savevm: Split load vm state function qemu_loadvm_state zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 29/32] COLO: Separate the process of saving/loading ram and device state zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 30/32] COLO: Split qemu_savevm_state_begin out of checkpoint process zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 31/32] COLO: Add block replication into colo process zhanghailiang
2015-09-02 8:23 ` [Qemu-devel] [PATCH COLO-Frame v9 32/32] COLO: Add net packets treatment into COLO zhanghailiang
2015-09-02 9:03 ` [Qemu-devel] [PATCH COLO-Frame v9 00/32] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service (FT) Yang Hongyang
2015-09-02 9:17 ` zhanghailiang
2015-09-09 3:36 ` zhanghailiang
2015-09-15 10:40 ` zhanghailiang
2015-10-21 14:10 ` Dr. David Alan Gilbert
2015-10-22 9:01 ` zhanghailiang
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=5625F591.5050601@huawei.com \
--to=zhang.zhanghailiang@huawei.com \
--cc=amit.shah@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=dgilbert@redhat.com \
--cc=eddie.dong@intel.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
--cc=yanghy@cn.fujitsu.com \
--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 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).