All of lore.kernel.org
 help / color / mirror / Atom feed
From: ChenLiang <chenliang88@huawei.com>
To: qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/6]  Obtain dirty bitmap via VM logging
Date: Wed, 21 May 2014 12:13:07 +0800	[thread overview]
Message-ID: <537C27D3.6070804@huawei.com> (raw)
In-Reply-To: <1400608075-19917-1-git-send-email-sanidhya.iiith@gmail.com>

Hi,
Nice job. We should avoid running migration_thread and bitmap_logging_thread simultaneously.

Best regards:
ChenLiang

> Hi,
> 
> This is the first part of my gsoc work.
> 
> Following patches add the support of dirty bitmap logging and dumping
> to a specified file. These patches provide the mechanism to get the
> dirty bitmap if the user wants to log the VM besides migration. This
> can be useful in case of learning about the writable working set of
> the VM even when it is not being migrated. I know that it will incur
> huge degradation but still, a user might want to do that. Besides this,
> this mechanism can also be useful in case of learning about the pages
> that can be stored in the cache while performing the xbzrle based live
> migration or even before the beginning of the hybrid (precopy + postcopy)
> live migration.
> 
> I have tried to provide both of the hmp and qmp commands interface to
> obtain the dirty bitmap. Besides dumping the dirty bitmap, one can
> also update the frequency with which the logging is taking place or
> even can cancel the ongoing logging process. Thus, there are 3 hmp and
> qmp commands interface provided to perform the task.
> 
> 
> Sanidhya Kashyap (6):
>   split dirty bitmap into four for dumping the bitmaps
>   bitmap dump code via QAPI framework
>   hmp interface for dirty bitmap dump
>   cancel mechanism for an already running dump bitmap process
>   set the frequency of the dump bitmap process
>   python script for extracting bitmap from a binary file
> 
>  exec.c                    |   4 +
>  hmp-commands.hx           |  46 +++++++
>  hmp.c                     |  36 +++++
>  hmp.h                     |   3 +
>  include/exec/memory.h     |   3 +-
>  include/exec/ram_addr.h   |  16 ++-
>  include/qapi/qmp/qerror.h |   3 +
>  qapi-schema.json          |  23 ++++
>  qmp-commands.hx           |  77 +++++++++++
>  savevm.c                  | 344 ++++++++++++++++++++++++++++++++++++++++++++++
>  scripts/extract-bitmap.py |  68 +++++++++
>  11 files changed, 621 insertions(+), 2 deletions(-)
>  create mode 100755 scripts/extract-bitmap.py
> 

  parent reply	other threads:[~2014-05-21  4:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20 17:47 [Qemu-devel] [PATCH 0/6] Obtain dirty bitmap via VM logging Sanidhya Kashyap
2014-05-20 17:47 ` [Qemu-devel] [PATCH 1/6] split dirty bitmap into four for dumping the bitmaps Sanidhya Kashyap
2014-05-20 17:47 ` [Qemu-devel] [PATCH 2/6] bitmap dump code via QAPI framework Sanidhya Kashyap
2014-05-20 19:03   ` Eric Blake
2014-05-20 19:25     ` Sanidhya Kashyap
2014-05-20 17:47 ` [Qemu-devel] [PATCH 3/6] hmp interface for dirty bitmap dump Sanidhya Kashyap
2014-05-20 17:47 ` [Qemu-devel] [PATCH 4/6] cancel mechanism for an already running dump bitmap process Sanidhya Kashyap
2014-05-20 19:34   ` Eric Blake
2014-05-20 17:47 ` [Qemu-devel] [PATCH 5/6] set the frequency of the " Sanidhya Kashyap
2014-05-20 19:36   ` Eric Blake
2014-05-20 17:47 ` [Qemu-devel] [PATCH 6/6] python script for extracting bitmap from a binary file Sanidhya Kashyap
2014-05-20 19:38   ` Eric Blake
2014-05-20 19:39     ` Eric Blake
2014-05-21  0:43       ` Sanidhya Kashyap
2014-05-21  4:13 ` ChenLiang [this message]
2014-05-21  4:56   ` [Qemu-devel] [PATCH 0/6] Obtain dirty bitmap via VM logging Sanidhya Kashyap
2014-05-21  6:45     ` ChenLiang
2014-05-21  6:55       ` Sanidhya Kashyap
2014-05-22 11:21       ` Sanidhya Kashyap
2014-05-22 12:57         ` ChenLiang
2014-05-23  2:30           ` Sanidhya Kashyap

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=537C27D3.6070804@huawei.com \
    --to=chenliang88@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.