qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Sanidhya Kashyap <sanidhya.iiith@gmail.com>
To: qemu list <qemu-devel@nongnu.org>
Cc: ChenLiang <chenliang88@huawei.com>,
	Sanidhya Kashyap <sanidhya.iiith@gmail.com>,
	Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] [PATCH 0/8] Obtain dirty bitmap via VM logging
Date: Mon, 26 May 2014 12:03:17 +0530	[thread overview]
Message-ID: <1401086005-8296-1-git-send-email-sanidhya.iiith@gmail.com> (raw)

Hi,

The following patches introduce the support of dirty bitmap logging and dumping
to a specified file. Still, some work is still left in the area of runstates that
I will try to work on after discussing this patch series.

v1 --> v2:
* Added two new run states to avoid simultaneous execution of both migration and
  bitmap dump process.
* Removed FILE pointer usage.
* Dumping the data only in machine-readable format.
* Tried to rectified mistakes of the previous version.



Sanidhya Kashyap (8):
  enable sharing of the function between migration and bitmap dump
  bitmap dump code via QAPI framework
  RunState: added two new flags for bitmap dump and migration process
  bitmap dump process with runstates
  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

 arch_init.c               |  19 +--
 hmp-commands.hx           |  45 +++++++
 hmp.c                     |  33 ++++++
 hmp.h                     |   3 +
 include/exec/ram_addr.h   |   4 +
 migration.c               |   7 ++
 qapi-schema.json          |  42 ++++++-
 qmp-commands.hx           |  76 ++++++++++++
 savevm.c                  | 290 ++++++++++++++++++++++++++++++++++++++++++++++
 scripts/extract-bitmap.py |  64 ++++++++++
 vl.c                      |  29 ++++-
 11 files changed, 602 insertions(+), 10 deletions(-)
 create mode 100755 scripts/extract-bitmap.py

-- 
1.8.3.1

             reply	other threads:[~2014-05-26  6:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26  6:33 Sanidhya Kashyap [this message]
2014-05-26  6:33 ` [Qemu-devel] [PATCH 1/8] enable sharing of the function between migration and bitmap dump Sanidhya Kashyap
2014-05-26  6:33 ` [Qemu-devel] [PATCH 2/8] bitmap dump code via QAPI framework Sanidhya Kashyap
2014-05-26  6:33 ` [Qemu-devel] [PATCH 3/8] RunState: added two new flags for bitmap dump and migration process Sanidhya Kashyap
2014-05-26  6:33 ` [Qemu-devel] [PATCH 4/8] bitmap dump process with runstates Sanidhya Kashyap
2014-05-26  6:33 ` [Qemu-devel] [PATCH 5/8] hmp interface for dirty bitmap dump Sanidhya Kashyap
2014-05-26  6:33 ` [Qemu-devel] [PATCH 6/8] cancel mechanism for an already running dump bitmap process Sanidhya Kashyap
2014-05-26  6:33 ` [Qemu-devel] [PATCH 7/8] set the frequency of the " Sanidhya Kashyap
2014-05-26  6:33 ` [Qemu-devel] [PATCH 8/8] python script for extracting bitmap from a binary file 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=1401086005-8296-1-git-send-email-sanidhya.iiith@gmail.com \
    --to=sanidhya.iiith@gmail.com \
    --cc=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 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).