From: Hailiang Zhang <zhang.zhanghailiang@huawei.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: xiecl.fnst@cn.fujitsu.com, lizhijian@cn.fujitsu.com,
quintela@redhat.com, armbru@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,
zhangchen.fnst@cn.fujitsu.com, hongyang.yang@easystack.cn
Subject: Re: [Qemu-devel] [PATCH COLO-Frame v15 29/38] COLO: Separate the process of saving/loading ram and device state
Date: Sat, 27 Feb 2016 18:03:47 +0800 [thread overview]
Message-ID: <56D17483.5050106@huawei.com> (raw)
In-Reply-To: <20160226131641.GF2161@work-vm>
On 2016/2/26 21:16, Dr. David Alan Gilbert wrote:
> * zhanghailiang (zhang.zhanghailiang@huawei.com) wrote:
>> We separate the process of saving/loading ram and device state when do
>> checkpoint, we add new helpers for save/load ram/device. With this change,
>> we can directly transfer ram from master to slave without using
>> QEMUSizeBufferas as assistant, which also reduce the size of extra memory
>> been used during checkpoint.
>>
>> Besides, we move the colo_flush_ram_cache to the proper position after the
>> above change.
>>
>> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
>> Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
>> ---
>> v14:
>> - split two new patches from this patch
>> - Some minor fixes from Dave
>> v13:
>> - Re-use some existed helper functions to realize saving/loading
>> ram and device.
>> v11:
>> - Remove load configuration section in qemu_loadvm_state_begin()
>> ---
>> migration/colo.c | 48 ++++++++++++++++++++++++++++++++++++++----------
>> migration/ram.c | 5 -----
>> migration/savevm.c | 5 +++++
>> 3 files changed, 43 insertions(+), 15 deletions(-)
>>
>> diff --git a/migration/colo.c b/migration/colo.c
>> index 16bada6..300fa54 100644
>> --- a/migration/colo.c
>> +++ b/migration/colo.c
>> @@ -288,21 +288,37 @@ static int colo_do_checkpoint_transaction(MigrationState *s,
>> goto out;
>> }
>>
>> + colo_put_cmd(s->to_dst_file, COLO_MESSAGE_VMSTATE_SEND, &local_err);
>> + if (local_err) {
>> + goto out;
>> + }
>> +
>> /* Disable block migration */
>> s->params.blk = 0;
>> s->params.shared = 0;
>> - qemu_savevm_state_header(trans);
>> - qemu_savevm_state_begin(trans, &s->params);
>> + qemu_savevm_state_begin(s->to_dst_file, &s->params);
>> + ret = qemu_file_get_error(s->to_dst_file);
>> + if (ret < 0) {
>> + error_report("Save vm state begin error");
>> + goto out;
>> + }
>> +
>> qemu_mutex_lock_iothread();
>> - qemu_savevm_state_complete_precopy(trans, false);
>> + /*
>> + * Only save VM's live state, which not including device state.
>> + * TODO: We may need a timeout mechanism to prevent COLO process
>> + * to be blocked here.
>> + */
>> + qemu_savevm_live_state(s->to_dst_file);
>> + /* Note: device state is saved into buffer */
>> + ret = qemu_save_device_state(trans);
>> qemu_mutex_unlock_iothread();
>
> Yes, I still worry a little about what can hang under that lock, but I think
Hmm, we have some other places in COLO taking this lock too. Some of them are
OK with holding it. But holding it while sending/receiving date from other side
in COLO is dangerous. One solution is to apply timeout for QEMUFile operation,
But it is not a good choice.
> it's the best we've got at the moment; we probably need to understand what
> the rules are about what actually needs the lock!
>
Yes, this is another way to solve the problem. Don't hold the lock while
sending/receiving date.
For qemu_savevm_live_state() here, IMHO, we can send the remained RAM data
without holding the global lock. Here we hold the lock, because we
call cpu_synchronize_all_states() in it. (I'm not sure ...)
Thanks,
Hailiang
> Other than that,
>
> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>
>> -
>> - qemu_fflush(trans);
>> -
>> - colo_put_cmd(s->to_dst_file, COLO_MESSAGE_VMSTATE_SEND, &local_err);
>> - if (local_err) {
>> + if (ret < 0) {
>> + error_report("Save device state error");
>> goto out;
>> }
>> + qemu_fflush(trans);
>> +
>> /* we send the total size of the vmstate first */
>> size = qsb_get_length(buffer);
>> colo_put_cmd_value(s->to_dst_file, COLO_MESSAGE_VMSTATE_SIZE,
>> @@ -573,6 +589,16 @@ void *colo_process_incoming_thread(void *opaque)
>> goto out;
>> }
>>
>> + ret = qemu_loadvm_state_begin(mis->from_src_file);
>> + if (ret < 0) {
>> + error_report("Load vm state begin error, ret=%d", ret);
>> + goto out;
>> + }
>> + ret = qemu_loadvm_state_main(mis->from_src_file, mis);
>> + if (ret < 0) {
>> + error_report("Load VM's live state (ram) error");
>> + goto out;
>> + }
>> /* read the VM state total size first */
>> value = colo_get_cmd_value(mis->from_src_file,
>> COLO_MESSAGE_VMSTATE_SIZE, &local_err);
>> @@ -605,8 +631,10 @@ void *colo_process_incoming_thread(void *opaque)
>> qemu_mutex_lock_iothread();
>> qemu_system_reset(VMRESET_SILENT);
>> vmstate_loading = true;
>> - if (qemu_loadvm_state(fb) < 0) {
>> - error_report("COLO: loadvm failed");
>> + colo_flush_ram_cache();
>> + ret = qemu_load_device_state(fb);
>> + if (ret < 0) {
>> + error_report("COLO: load device state failed");
>> qemu_mutex_unlock_iothread();
>> goto out;
>> }
>> diff --git a/migration/ram.c b/migration/ram.c
>> index 891f3b2..8f416d5 100644
>> --- a/migration/ram.c
>> +++ b/migration/ram.c
>> @@ -2465,7 +2465,6 @@ static int ram_load(QEMUFile *f, void *opaque, int version_id)
>> * be atomic
>> */
>> bool postcopy_running = postcopy_state_get() >= POSTCOPY_INCOMING_LISTENING;
>> - bool need_flush = false;
>>
>> seq_iter++;
>>
>> @@ -2500,7 +2499,6 @@ static int ram_load(QEMUFile *f, void *opaque, int version_id)
>> /* After going into COLO, we should load the Page into colo_cache */
>> if (ram_cache_enable) {
>> host = colo_cache_from_block_offset(block, addr);
>> - need_flush = true;
>> } else {
>> host = host_from_ram_block_offset(block, addr);
>> }
>> @@ -2594,9 +2592,6 @@ static int ram_load(QEMUFile *f, void *opaque, int version_id)
>>
>> rcu_read_unlock();
>>
>> - if (!ret && ram_cache_enable && need_flush) {
>> - colo_flush_ram_cache();
>> - }
>> DPRINTF("Completed load of VM with exit code %d seq iteration "
>> "%" PRIu64 "\n", ret, seq_iter);
>> return ret;
>> diff --git a/migration/savevm.c b/migration/savevm.c
>> index 60c7b57..1551fbb 100644
>> --- a/migration/savevm.c
>> +++ b/migration/savevm.c
>> @@ -50,6 +50,7 @@
>> #include "qemu/iov.h"
>> #include "block/snapshot.h"
>> #include "block/qapi.h"
>> +#include "migration/colo.h"
>>
>>
>> #ifndef ETH_P_RARP
>> @@ -923,6 +924,10 @@ void qemu_savevm_state_begin(QEMUFile *f,
>> break;
>> }
>> }
>> + if (migration_in_colo_state()) {
>> + qemu_put_byte(f, QEMU_VM_EOF);
>> + qemu_fflush(f);
>> + }
>> }
>>
>> /*
>> --
>> 1.8.3.1
>>
>>
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>
> .
>
next prev parent reply other threads:[~2016-02-27 10:04 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 2:39 [Qemu-devel] [PATCH COLO-Frame v15 00/38] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service (FT) zhanghailiang
2016-02-22 2:39 ` [Qemu-devel] [PATCH COLO-Frame v15 01/38] configure: Add parameter for configure to enable/disable COLO support zhanghailiang
2016-02-22 2:39 ` [Qemu-devel] [PATCH COLO-Frame v15 02/38] migration: Introduce capability 'x-colo' to migration zhanghailiang
2016-02-22 2:39 ` [Qemu-devel] [PATCH COLO-Frame v15 03/38] COLO: migrate colo related info to secondary node zhanghailiang
2016-02-22 2:39 ` [Qemu-devel] [PATCH COLO-Frame v15 04/38] migration: Integrate COLO checkpoint process into migration zhanghailiang
2016-02-22 2:39 ` [Qemu-devel] [PATCH COLO-Frame v15 05/38] migration: Integrate COLO checkpoint process into loadvm zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 06/38] COLO/migration: Create a new communication path from destination to source zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 07/38] COLO: Implement colo checkpoint protocol zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 08/38] COLO: Add a new RunState RUN_STATE_COLO zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 09/38] QEMUSizedBuffer: Introduce two help functions for qsb zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 10/38] COLO: Save PVM state to secondary side when do checkpoint zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 11/38] COLO: Load PVM's dirty pages into SVM's RAM cache temporarily zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 12/38] ram/COLO: Record the dirty pages that SVM received zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 13/38] COLO: Load VMState into qsb before restore it zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 14/38] COLO: Flush PVM's cached RAM into SVM's memory zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 15/38] COLO: Add checkpoint-delay parameter for migrate-set-parameters zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 16/38] COLO: synchronize PVM's state to SVM periodically zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 17/38] COLO failover: Introduce a new command to trigger a failover zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 18/38] COLO failover: Introduce state to record failover process zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 19/38] COLO: Implement failover work for Primary VM zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 20/38] COLO: Implement failover work for Secondary VM zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 21/38] qmp event: Add COLO_EXIT event to notify users while exited from COLO zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 22/38] COLO failover: Shutdown related socket fd when do failover zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 23/38] COLO failover: Don't do failover during loading VM's state zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 24/38] COLO: Process shutdown command for VM in COLO state zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 25/38] COLO: Update the global runstate after going into colo state zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 26/38] savevm: Introduce two helper functions for save/find loadvm_handlers entry zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 27/38] migration/savevm: Add new helpers to process the different stages of loadvm zhanghailiang
2016-02-26 12:52 ` Dr. David Alan Gilbert
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 28/38] migration/savevm: Export two helper functions for savevm process zhanghailiang
2016-02-26 13:00 ` Dr. David Alan Gilbert
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 29/38] COLO: Separate the process of saving/loading ram and device state zhanghailiang
2016-02-26 13:16 ` Dr. David Alan Gilbert
2016-02-27 10:03 ` Hailiang Zhang [this message]
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 30/38] COLO: Split qemu_savevm_state_begin out of checkpoint process zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 31/38] net/filter: Add a 'status' property for filter object zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 32/38] filter-buffer: Accept zero interval zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 33/38] net: Add notifier/callback for netdev init zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 34/38] COLO/filter: add each netdev a buffer filter zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 35/38] COLO: manage the status of buffer filters for PVM zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 36/38] filter-buffer: make filter_buffer_flush() public zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 37/38] COLO: flush buffered packets in checkpoint process or exit COLO zhanghailiang
2016-02-22 2:40 ` [Qemu-devel] [PATCH COLO-Frame v15 38/38] COLO: Add block replication into colo process zhanghailiang
2016-02-25 19:52 ` [Qemu-devel] [PATCH COLO-Frame v15 00/38] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service (FT) Dr. David Alan Gilbert
2016-02-26 16:36 ` Dr. David Alan Gilbert
2016-02-27 7:54 ` Hailiang Zhang
2016-02-29 9:47 ` Dr. David Alan Gilbert
2016-02-29 12:16 ` Hailiang Zhang
2016-02-29 13:04 ` Dr. David Alan Gilbert
2016-03-01 12:25 ` Dr. David Alan Gilbert
2016-03-02 13:01 ` Hailiang Zhang
2016-03-03 20:13 ` Dr. David Alan Gilbert
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=56D17483.5050106@huawei.com \
--to=zhang.zhanghailiang@huawei.com \
--cc=amit.shah@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eddie.dong@intel.com \
--cc=hongyang.yang@easystack.cn \
--cc=lizhijian@cn.fujitsu.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
--cc=xiecl.fnst@cn.fujitsu.com \
--cc=yunhong.jiang@intel.com \
--cc=zhangchen.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).