From: Zhang Chen <zhangckid@gmail.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
zhanghailiang <zhang.zhanghailiang@huawei.com>,
Juan Quintela <quintela@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Jason Wang <jasowang@redhat.com>, Eric Blake <eblake@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Zhang Chen <zhangckid@gmail.com>,
Li Zhijian <lizhijian@cn.fujitsu.com>
Subject: [Qemu-devel] [PATCH V5 08/17] ram/COLO: Record the dirty pages that SVM received
Date: Sun, 11 Mar 2018 05:21:58 +0800 [thread overview]
Message-ID: <1520716927-17068-9-git-send-email-zhangckid@gmail.com> (raw)
In-Reply-To: <1520716927-17068-1-git-send-email-zhangckid@gmail.com>
We record the address of the dirty pages that received,
it will help flushing pages that cached into SVM.
Here, it is a trick, we record dirty pages by re-using migration
dirty bitmap. In the later patch, we will start the dirty log
for SVM, just like migration, in this way, we can record both
the dirty pages caused by PVM and SVM, we only flush those dirty
pages from RAM cache while do checkpoint.
Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
---
migration/ram.c | 33 +++++++++++++++++++++++++++++++++
1 file changed, 33 insertions(+)
diff --git a/migration/ram.c b/migration/ram.c
index 86f5c3c..4534c7a 100644
--- a/migration/ram.c
+++ b/migration/ram.c
@@ -2481,6 +2481,15 @@ static inline void *colo_cache_from_block_offset(RAMBlock *block,
__func__, block->idstr);
return NULL;
}
+
+ /*
+ * During colo checkpoint, we need bitmap of these migrated pages.
+ * It help us to decide which pages in ram cache should be flushed
+ * into VM's RAM later.
+ */
+ if (!test_and_set_bit(offset >> TARGET_PAGE_BITS, block->bmap)) {
+ ram_state->migration_dirty_pages++;
+ }
return block->colo_cache + offset;
}
@@ -2659,6 +2668,24 @@ int colo_init_ram_cache(void)
}
}
rcu_read_unlock();
+ /*
+ * Record the dirty pages that sent by PVM, we use this dirty bitmap together
+ * with to decide which page in cache should be flushed into SVM's RAM. Here
+ * we use the same name 'ram_bitmap' as for migration.
+ */
+ if (ram_bytes_total()) {
+ RAMBlock *block;
+
+ QLIST_FOREACH_RCU(block, &ram_list.blocks, next) {
+ unsigned long pages = block->max_length >> TARGET_PAGE_BITS;
+
+ block->bmap = bitmap_new(pages);
+ bitmap_set(block->bmap, 0, pages);
+ }
+ }
+ ram_state = g_new0(RAMState, 1);
+ ram_state->migration_dirty_pages = 0;
+
return 0;
out_locked:
@@ -2678,6 +2705,10 @@ void colo_release_ram_cache(void)
{
RAMBlock *block;
+ QLIST_FOREACH_RCU(block, &ram_list.blocks, next) {
+ g_free(block->bmap);
+ block->bmap = NULL;
+ }
rcu_read_lock();
QLIST_FOREACH_RCU(block, &ram_list.blocks, next) {
if (block->colo_cache) {
@@ -2686,6 +2717,8 @@ void colo_release_ram_cache(void)
}
}
rcu_read_unlock();
+ g_free(ram_state);
+ ram_state = NULL;
}
/**
--
2.7.4
next prev parent reply other threads:[~2018-03-10 21:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-10 21:21 [Qemu-devel] [PATCH V5 00/17] COLO: integrate colo frame with block replication and COLO proxy Zhang Chen
2018-03-10 21:21 ` [Qemu-devel] [PATCH V5 01/17] filter-rewriter: fix memory leak for connection in connection_track_table Zhang Chen
2018-03-10 21:21 ` [Qemu-devel] [PATCH V5 02/17] colo-compare: implement the process of checkpoint Zhang Chen
2018-03-10 21:21 ` [Qemu-devel] [PATCH V5 03/17] colo-compare: use notifier to notify packets comparing result Zhang Chen
2018-03-10 21:21 ` [Qemu-devel] [PATCH V5 04/17] COLO: integrate colo compare with colo frame Zhang Chen
2018-03-10 21:21 ` [Qemu-devel] [PATCH V5 05/17] COLO: Add block replication into colo process Zhang Chen
2018-03-10 21:21 ` [Qemu-devel] [PATCH V5 06/17] COLO: Remove colo_state migration struct Zhang Chen
2018-03-10 21:21 ` [Qemu-devel] [PATCH V5 07/17] COLO: Load dirty pages into SVM's RAM cache firstly Zhang Chen
2018-03-10 21:21 ` Zhang Chen [this message]
2018-03-10 21:21 ` [Qemu-devel] [PATCH V5 09/17] COLO: Flush memory data from ram cache Zhang Chen
2018-03-10 21:22 ` [Qemu-devel] [PATCH V5 10/17] qmp event: Add COLO_EXIT event to notify users while exited COLO Zhang Chen
2018-03-10 21:22 ` [Qemu-devel] [PATCH V5 11/17] qapi: Add new command to query colo status Zhang Chen
2018-03-10 21:33 ` Eric Blake
2018-03-11 7:59 ` Zhang Chen
2018-03-10 21:22 ` [Qemu-devel] [PATCH V5 12/17] savevm: split the process of different stages for loadvm/savevm Zhang Chen
2018-03-10 21:22 ` [Qemu-devel] [PATCH V5 13/17] COLO: flush host dirty ram from cache Zhang Chen
2018-03-10 21:22 ` [Qemu-devel] [PATCH V5 14/17] filter: Add handle_event method for NetFilterClass Zhang Chen
2018-03-10 21:22 ` [Qemu-devel] [PATCH V5 15/17] filter-rewriter: handle checkpoint and failover event Zhang Chen
2018-03-10 21:22 ` [Qemu-devel] [PATCH V5 16/17] COLO: notify net filters about checkpoint/failover event Zhang Chen
2018-03-10 21:22 ` [Qemu-devel] [PATCH V5 17/17] COLO: quick failover process by kick COLO thread Zhang Chen
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=1520716927-17068-9-git-send-email-zhangckid@gmail.com \
--to=zhangckid@gmail.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=jasowang@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=zhang.zhanghailiang@huawei.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).