From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: zhanghailiang <zhang.zhanghailiang@huawei.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, amit.shah@redhat.com,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Yang Hongyang <yanghy@cn.fujitsu.com>,
david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [RFC PATCH v4 09/28] COLO: Save VM state to slave when do checkpoint
Date: Mon, 18 May 2015 13:10:20 +0100 [thread overview]
Message-ID: <20150518121019.GB14465@work-vm> (raw)
In-Reply-To: <5559ACCB.3020308@huawei.com>
* zhanghailiang (zhang.zhanghailiang@huawei.com) wrote:
> On 2015/5/15 20:09, Dr. David Alan Gilbert wrote:
> >* zhanghailiang (zhang.zhanghailiang@huawei.com) wrote:
> >>We should save PVM's RAM/device to slave when needed.
> >>
> >>For VM state, we will cache them in slave, we use QEMUSizedBuffer
> >>to store the data, we need know the data size of VM state, so in master,
> >>we use qsb to store VM state temporarily, and then migrate the data to
> >>slave.
> >>
> >>Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
> >>Signed-off-by: Yang Hongyang <yanghy@cn.fujitsu.com>
> >>Signed-off-by: Gonglei <arei.gonglei@huawei.com>
> >>Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> >>Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
> >>---
> >> arch_init.c | 22 ++++++++++++++++++--
> >> migration/colo.c | 62 ++++++++++++++++++++++++++++++++++++++++++++++++++++----
> >> savevm.c | 2 +-
> >> 3 files changed, 79 insertions(+), 7 deletions(-)
> >>
> >>diff --git a/arch_init.c b/arch_init.c
> >>index fcfa328..e928e11 100644
> >>--- a/arch_init.c
> >>+++ b/arch_init.c
> >>@@ -53,6 +53,7 @@
> >> #include "hw/acpi/acpi.h"
> >> #include "qemu/host-utils.h"
> >> #include "qemu/rcu_queue.h"
> >>+#include "migration/migration-colo.h"
> >>
> >> #ifdef DEBUG_ARCH_INIT
> >> #define DPRINTF(fmt, ...) \
> >>@@ -845,6 +846,13 @@ static int ram_save_setup(QEMUFile *f, void *opaque)
> >> RAMBlock *block;
> >> int64_t ram_bitmap_pages; /* Size of bitmap in pages, including gaps */
> >>
> >>+ /*
> >>+ * migration has already setup the bitmap, reuse it.
> >>+ */
> >>+ if (migrate_in_colo_state()) {
> >>+ goto setup_part;
> >>+ }
> >>+
> >
> >This is a bit odd. It would be easier if you just moved the init code
> >inside this if, rather than goto'ing over it (or move the other code that
> >you actually want into another function that then gets called from the bottom
> >of here?)
> >The thing that also makes it especially odd is that you goto over
> >the rcu_read_lock and then have to fix it up; that's getting messy.
> >
>
> Yes, here we reuse ram_save_setup in COLO's checkpoint process, the difference is
> in COLO's checkpoint process, we don't have to initialize these global variables again,
> which has been initialized in the previous first migration process. But we have to resend
> the info of ram_list.blocks. (Maybe this also not necessary ). I will split this function temporarily
> to make this look gentler.
Great.
> >(The qemu style seems to be OK to use goto to jump to a shared error
> >block at the end of a function but otherwise it should be rare).
> >
> >> mig_throttle_on = false;
> >> dirty_rate_high_cnt = 0;
> >> bitmap_sync_count = 0;
> >>@@ -901,9 +909,12 @@ static int ram_save_setup(QEMUFile *f, void *opaque)
> >> migration_bitmap_sync();
> >> qemu_mutex_unlock_ramlist();
> >> qemu_mutex_unlock_iothread();
> >>-
> >>+setup_part:
> >> qemu_put_be64(f, ram_bytes_total() | RAM_SAVE_FLAG_MEM_SIZE);
> >>
> >>+ if (migrate_in_colo_state()) {
> >>+ rcu_read_lock();
> >>+ }
> >> QLIST_FOREACH_RCU(block, &ram_list.blocks, next) {
> >> qemu_put_byte(f, strlen(block->idstr));
> >> qemu_put_buffer(f, (uint8_t *)block->idstr, strlen(block->idstr));
> >>@@ -1007,7 +1018,14 @@ static int ram_save_complete(QEMUFile *f, void *opaque)
> >> }
> >>
> >> ram_control_after_iterate(f, RAM_CONTROL_FINISH);
> >>- migration_end();
> >>+
> >>+ /*
> >>+ * Since we need to reuse dirty bitmap in colo,
> >>+ * don't cleanup the bitmap.
> >>+ */
> >>+ if (!migrate_enable_colo() || migration_has_failed(migrate_get_current())) {
> >>+ migration_end();
> >>+ }
> >>
> >> rcu_read_unlock();
> >> qemu_put_be64(f, RAM_SAVE_FLAG_EOS);
> >>diff --git a/migration/colo.c b/migration/colo.c
> >>index 5a8ed1b..64e3f3a 100644
> >>--- a/migration/colo.c
> >>+++ b/migration/colo.c
> >>@@ -60,6 +60,9 @@ enum {
> >>
> >> static QEMUBH *colo_bh;
> >> static Coroutine *colo;
> >>+/* colo buffer */
> >>+#define COLO_BUFFER_BASE_SIZE (1000*1000*4ULL)
> >
> >Surely you want that as 4*1024*1024 ? Anyway, now that qemu has
> >migrate_set_parameter, it's probably best to wire these magic numbers
> >to parameters that can be configured.
> >
>
> Er, actually this macro can be any value, it does not matter, because qsb will grow automatically
> if the size of qsb is not enough. (Am i right?).
> And i don't think this internal used value should be exported to user. For now this size include
> the size of dirty pages and the size of device related data.
Yes, you're right; (However I'd still use a power of 2 for a size for memory, but maybe
that's just me)
> But, maybe i can use the new
> 'migrate_set_parameter' to achieve the capability of 'colo_set_checkpoint_period'.
Yes, it's good for that.
Dave
>
>
> Thanks,
> zhanghailiang
>
> >>+QEMUSizedBuffer *colo_buffer;
> >>
> >> bool colo_supported(void)
> >> {
> >>@@ -123,6 +126,8 @@ static int colo_ctl_get(QEMUFile *f, uint64_t require)
> >> static int colo_do_checkpoint_transaction(MigrationState *s, QEMUFile *control)
> >> {
> >> int ret;
> >>+ size_t size;
> >>+ QEMUFile *trans = NULL;
> >>
> >> ret = colo_ctl_put(s->file, COLO_CHECKPOINT_NEW);
> >> if (ret < 0) {
> >>@@ -133,16 +138,47 @@ static int colo_do_checkpoint_transaction(MigrationState *s, QEMUFile *control)
> >> if (ret < 0) {
> >> goto out;
> >> }
> >>+ /* Reset colo buffer and open it for write */
> >>+ qsb_set_length(colo_buffer, 0);
> >>+ trans = qemu_bufopen("w", colo_buffer);
> >>+ if (!trans) {
> >>+ error_report("Open colo buffer for write failed");
> >>+ goto out;
> >>+ }
> >>+
> >>+ /* suspend and save vm state to colo buffer */
> >>+ qemu_mutex_lock_iothread();
> >>+ vm_stop_force_state(RUN_STATE_COLO);
> >>+ qemu_mutex_unlock_iothread();
> >>+ DPRINTF("vm is stoped\n");
> >>+
> >>+ /* Disable block migration */
> >>+ s->params.blk = 0;
> >>+ s->params.shared = 0;
> >>+ qemu_savevm_state_begin(trans, &s->params);
> >>+ qemu_mutex_lock_iothread();
> >>+ qemu_savevm_state_complete(trans);
> >>+ qemu_mutex_unlock_iothread();
> >>
> >>- /* TODO: suspend and save vm state to colo buffer */
> >>+ qemu_fflush(trans);
> >>
> >> ret = colo_ctl_put(s->file, COLO_CHECKPOINT_SEND);
> >> if (ret < 0) {
> >> goto out;
> >> }
> >>+ /* we send the total size of the vmstate first */
> >>+ size = qsb_get_length(colo_buffer);
> >>+ ret = colo_ctl_put(s->file, size);
> >>+ if (ret < 0) {
> >>+ goto out;
> >>+ }
> >>
> >>- /* TODO: send vmstate to slave */
> >>-
> >>+ qsb_put_buffer(s->file, colo_buffer, size);
> >>+ qemu_fflush(s->file);
> >>+ ret = qemu_file_get_error(s->file);
> >>+ if (ret < 0) {
> >>+ goto out;
> >>+ }
> >> ret = colo_ctl_get(control, COLO_CHECKPOINT_RECEIVED);
> >> if (ret < 0) {
> >> goto out;
> >>@@ -154,9 +190,18 @@ static int colo_do_checkpoint_transaction(MigrationState *s, QEMUFile *control)
> >> }
> >> DPRINTF("got COLO_CHECKPOINT_LOADED\n");
> >>
> >>- /* TODO: resume master */
> >>+ ret = 0;
> >>+ /* resume master */
> >>+ qemu_mutex_lock_iothread();
> >>+ vm_start();
> >>+ qemu_mutex_unlock_iothread();
> >>+ DPRINTF("vm resume to run again\n");
> >>
> >> out:
> >>+ if (trans) {
> >>+ qemu_fclose(trans);
> >>+ }
> >>+
> >> return ret;
> >> }
> >>
> >>@@ -182,6 +227,12 @@ static void *colo_thread(void *opaque)
> >> }
> >> DPRINTF("get COLO_READY\n");
> >>
> >>+ colo_buffer = qsb_create(NULL, COLO_BUFFER_BASE_SIZE);
> >>+ if (colo_buffer == NULL) {
> >>+ error_report("Failed to allocate colo buffer!");
> >>+ goto out;
> >>+ }
> >>+
> >> qemu_mutex_lock_iothread();
> >> vm_start();
> >> qemu_mutex_unlock_iothread();
> >>@@ -197,6 +248,9 @@ static void *colo_thread(void *opaque)
> >> out:
> >> migrate_set_state(s, MIGRATION_STATUS_COLO, MIGRATION_STATUS_COMPLETED);
> >>
> >>+ qsb_free(colo_buffer);
> >>+ colo_buffer = NULL;
> >>+
> >> if (colo_control) {
> >> qemu_fclose(colo_control);
> >> }
> >>diff --git a/savevm.c b/savevm.c
> >>index 3b0e222..cd7ec27 100644
> >>--- a/savevm.c
> >>+++ b/savevm.c
> >>@@ -42,7 +42,7 @@
> >> #include "qemu/iov.h"
> >> #include "block/snapshot.h"
> >> #include "block/qapi.h"
> >>-
> >>+#include "migration/migration-colo.h"
> >>
> >> #ifndef ETH_P_RARP
> >> #define ETH_P_RARP 0x8035
> >>--
> >>1.7.12.4
> >>
> >>
> >--
> >Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> >
> >.
> >
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2015-05-18 12:10 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 5:29 [Qemu-devel] [RFC PATCH v4 00/28] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 01/28] configure: Add parameter for configure to enable/disable COLO support zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 02/28] migration: Introduce capability 'colo' to migration zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 03/28] COLO: migrate colo related info to slave zhanghailiang
2015-05-15 11:38 ` Dr. David Alan Gilbert
2015-05-18 5:04 ` zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 04/28] migration: Integrate COLO checkpoint process into migration zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 05/28] migration: Integrate COLO checkpoint process into loadvm zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 06/28] COLO: Implement colo checkpoint protocol zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 07/28] COLO: Add a new RunState RUN_STATE_COLO zhanghailiang
2015-05-15 11:28 ` Dr. David Alan Gilbert
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 08/28] QEMUSizedBuffer: Introduce two help functions for qsb zhanghailiang
2015-05-15 11:56 ` Dr. David Alan Gilbert
2015-05-18 5:10 ` zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 09/28] COLO: Save VM state to slave when do checkpoint zhanghailiang
2015-05-15 12:09 ` Dr. David Alan Gilbert
2015-05-18 9:11 ` zhanghailiang
2015-05-18 12:10 ` Dr. David Alan Gilbert [this message]
2015-05-18 12:22 ` zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 10/28] COLO RAM: Load PVM's dirty page into SVM's RAM cache temporarily zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 11/28] COLO VMstate: Load VM state into qsb before restore it zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 12/28] arch_init: Start to trace dirty pages of SVM zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 13/28] COLO RAM: Flush cached RAM into SVM's memory zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 14/28] COLO failover: Introduce a new command to trigger a failover zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 15/28] COLO failover: Implement COLO master/slave failover work zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 16/28] COLO failover: Don't do failover during loading VM's state zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 17/28] COLO: Add new command parameter 'colo_nicname' 'colo_script' for net zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 18/28] COLO NIC: Init/remove colo nic devices when add/cleanup tap devices zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 19/28] COLO NIC: Implement colo nic device interface configure() zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 20/28] COLO NIC : Implement colo nic init/destroy function zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 21/28] COLO NIC: Some init work related with proxy module zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 22/28] COLO: Do checkpoint according to the result of net packets comparing zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 23/28] COLO: Improve checkpoint efficiency by do additional periodic checkpoint zhanghailiang
2015-05-18 16:48 ` Dr. David Alan Gilbert
2015-05-19 6:08 ` zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 24/28] COLO: Add colo-set-checkpoint-period command zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 25/28] COLO NIC: Implement NIC checkpoint and failover zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 26/28] COLO: Disable qdev hotplug when VM is in COLO mode zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 27/28] COLO: Implement shutdown checkpoint zhanghailiang
2015-03-26 5:29 ` [Qemu-devel] [RFC PATCH v4 28/28] COLO: Add block replication into colo process zhanghailiang
2015-04-08 8:16 ` [Qemu-devel] [RFC PATCH v4 00/28] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service zhanghailiang
2015-04-22 11:18 ` Dr. David Alan Gilbert
2015-04-24 7:25 ` Wen Congyang
2015-04-24 8:35 ` Dr. David Alan Gilbert
2015-04-28 10:51 ` zhanghailiang
2015-05-06 17:11 ` Dr. David Alan Gilbert
2015-04-24 8:52 ` zhanghailiang
2015-04-24 8:56 ` Dr. David Alan Gilbert
2015-05-14 12:14 ` Dr. David Alan Gilbert
2015-05-14 12:58 ` zhanghailiang
2015-05-14 16:09 ` 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=20150518121019.GB14465@work-vm \
--to=dgilbert@redhat.com \
--cc=amit.shah@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=david@gibson.dropbear.id.au \
--cc=eddie.dong@intel.com \
--cc=laijs@cn.fujitsu.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=yanghy@cn.fujitsu.com \
--cc=yunhong.jiang@intel.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).