From: Hailiang Zhang <zhang.zhanghailiang@huawei.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: xuquan8@huawei.com, qemu-devel@nongnu.org,
zhangchen.fnst@cn.fujitsu.com, lizhijian@cn.fujitsu.com,
xiecl.fnst@cn.fujitsu.com, Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 15/15] COLO: flush host dirty ram from cache
Date: Mon, 10 Apr 2017 15:13:58 +0800 [thread overview]
Message-ID: <58EB30B6.60603@huawei.com> (raw)
In-Reply-To: <20170407173902.GP2138@work-vm>
On 2017/4/8 1:39, Dr. David Alan Gilbert wrote:
> * zhanghailiang (zhang.zhanghailiang@huawei.com) wrote:
>> Don't need to flush all VM's ram from cache, only
>> flush the dirty pages since last checkpoint
>>
>> Cc: Juan Quintela <quintela@redhat.com>
>> Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
>> Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
>> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
>> ---
>> migration/ram.c | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/migration/ram.c b/migration/ram.c
>> index 6227b94..e9ba740 100644
>> --- a/migration/ram.c
>> +++ b/migration/ram.c
>> @@ -2702,6 +2702,7 @@ int colo_init_ram_cache(void)
>> migration_bitmap_rcu = g_new0(struct BitmapRcu, 1);
>> migration_bitmap_rcu->bmap = bitmap_new(ram_cache_pages);
>> migration_dirty_pages = 0;
>> + memory_global_dirty_log_start();
> Shouldn't there be a stop somewhere?
> (Probably if you failover to the secondary and colo stops?)
Ha, good catch, i forgot to stop the dirty log in secondary side.
>> return 0;
>>
>> @@ -2750,6 +2751,15 @@ void colo_flush_ram_cache(void)
>> void *src_host;
>> ram_addr_t offset = 0;
>>
>> + memory_global_dirty_log_sync();
>> + qemu_mutex_lock(&migration_bitmap_mutex);
>> + rcu_read_lock();
>> + QLIST_FOREACH_RCU(block, &ram_list.blocks, next) {
>> + migration_bitmap_sync_range(block->offset, block->used_length);
>> + }
>> + rcu_read_unlock();
>> + qemu_mutex_unlock(&migration_bitmap_mutex);
> Again this might have some fun merging with Juan's recent changes - what's
> really unusual about your set is that you're using this bitmap on the destination;
> I suspect Juan's recent changes that trickier.
> Check 'Creating RAMState for migration' and 'Split migration bitmaps by ramblock'.
I have reviewed these two series, and i think it's not a big problem
for COLO here, We can still re-use most of the codes.
Thanks,
Hailiang
> Dave
>> trace_colo_flush_ram_cache_begin(migration_dirty_pages);
>> rcu_read_lock();
>> block = QLIST_FIRST_RCU(&ram_list.blocks);
>> --
>> 1.8.3.1
>>
>>
>>
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>
> .
>
prev parent reply other threads:[~2017-04-10 7:15 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 3:42 [Qemu-devel] [PATCH 00/15] COLO: integrate colo frame with block replication and net compare zhanghailiang
2017-02-22 3:42 ` [Qemu-devel] [PATCH 01/15] net/colo: Add notifier/callback related helpers for filter zhanghailiang
2017-04-07 15:46 ` Dr. David Alan Gilbert
2017-04-10 7:26 ` Hailiang Zhang
2017-02-22 3:42 ` [Qemu-devel] [PATCH 02/15] colo-compare: implement the process of checkpoint zhanghailiang
2017-02-22 9:31 ` Zhang Chen
2017-02-23 1:02 ` Hailiang Zhang
2017-02-23 5:49 ` Zhang Chen
2017-04-14 5:57 ` Jason Wang
2017-04-14 6:22 ` Hailiang Zhang
2017-04-14 6:38 ` Jason Wang
2017-04-17 11:04 ` Hailiang Zhang
2017-04-18 1:32 ` Zhang Chen
2017-04-18 3:55 ` Jason Wang
2017-04-18 6:58 ` Hailiang Zhang
2017-04-20 5:15 ` Jason Wang
2017-04-21 8:10 ` Hailiang Zhang
2017-02-22 3:42 ` [Qemu-devel] [PATCH 03/15] colo-compare: use notifier to notify packets comparing result zhanghailiang
2017-02-22 3:42 ` [Qemu-devel] [PATCH 04/15] COLO: integrate colo compare with colo frame zhanghailiang
2017-04-07 15:59 ` Dr. David Alan Gilbert
2017-02-22 3:42 ` [Qemu-devel] [PATCH 05/15] COLO: Handle shutdown command for VM in COLO state zhanghailiang
2017-02-22 15:35 ` Eric Blake
2017-02-23 1:15 ` Hailiang Zhang
2017-02-22 3:42 ` [Qemu-devel] [PATCH 06/15] COLO: Add block replication into colo process zhanghailiang
2017-02-22 3:42 ` [Qemu-devel] [PATCH 07/15] COLO: Load PVM's dirty pages into SVM's RAM cache temporarily zhanghailiang
2017-04-07 17:06 ` Dr. David Alan Gilbert
2017-04-10 7:31 ` Hailiang Zhang
2017-02-22 3:42 ` [Qemu-devel] [PATCH 08/15] ram/COLO: Record the dirty pages that SVM received zhanghailiang
2017-02-23 18:44 ` Dr. David Alan Gilbert
2017-02-22 3:42 ` [Qemu-devel] [PATCH 09/15] COLO: Flush PVM's cached RAM into SVM's memory zhanghailiang
2017-02-22 3:42 ` [Qemu-devel] [PATCH 10/15] qmp event: Add COLO_EXIT event to notify users while exited from COLO zhanghailiang
2017-02-22 3:42 ` [Qemu-devel] [PATCH 11/15] savevm: split save/find loadvm_handlers entry into two helper functions zhanghailiang
2017-02-22 3:42 ` [Qemu-devel] [PATCH 12/15] savevm: split the process of different stages for loadvm/savevm zhanghailiang
2017-04-07 17:18 ` Dr. David Alan Gilbert
2017-04-10 8:26 ` Hailiang Zhang
2017-04-20 9:09 ` Dr. David Alan Gilbert
2017-04-21 6:50 ` Hailiang Zhang
2017-02-22 3:42 ` [Qemu-devel] [PATCH 13/15] COLO: Separate the process of saving/loading ram and device state zhanghailiang
2017-02-22 3:42 ` [Qemu-devel] [PATCH 14/15] COLO: Split qemu_savevm_state_begin out of checkpoint process zhanghailiang
2017-02-22 3:42 ` [Qemu-devel] [PATCH 15/15] COLO: flush host dirty ram from cache zhanghailiang
2017-04-07 17:39 ` Dr. David Alan Gilbert
2017-04-10 7:13 ` Hailiang Zhang [this message]
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=58EB30B6.60603@huawei.com \
--to=zhang.zhanghailiang@huawei.com \
--cc=dgilbert@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=xiecl.fnst@cn.fujitsu.com \
--cc=xuquan8@huawei.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).