From: Sanidhya Kashyap <sanidhya.iiith@gmail.com>
To: qemu list <qemu-devel@nongnu.org>
Cc: Sanidhya Kashyap <sanidhya.iiith@gmail.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/7] Obtain dirty bitmap via VM logging
Date: Thu, 12 Jun 2014 16:06:33 +0530 [thread overview]
Message-ID: <1402569400-12242-1-git-send-email-sanidhya.iiith@gmail.com> (raw)
Hi,
The following patches introduce the support of the dirty bitmap logging and
dumping to a specified file. This patch addresses the issues raised by David
and Juan. Since, I have not received any comments on the runstates, I'll keep
them in the patch series.
v2 --> v3
* Reformatted the code and removed some unnecessary parts.
* Printing block info along with length and offset.
* Changed the functions that were directly using RUN_STATE_RUNNING as state.
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 rectify mistakes of the previous version.
Sanidhya Kashyap (7):
enable sharing of the function between migration and bitmap dump
RunState: added two new flags for bitmap dump and migration process
bitmap dump code via QAPI framework 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 +
hw/usb/hcd-ehci.c | 2 +-
hw/usb/redirect.c | 6 +-
include/exec/cpu-all.h | 3 +-
include/exec/ram_addr.h | 4 +
migration.c | 7 +
qapi-schema.json | 44 +++++-
qmp-commands.hx | 77 ++++++++++
savevm.c | 357 ++++++++++++++++++++++++++++++++++++++++++++++
scripts/extract-bitmap.py | 97 +++++++++++++
vl.c | 29 +++-
14 files changed, 711 insertions(+), 15 deletions(-)
create mode 100755 scripts/extract-bitmap.py
--
1.9.3
next reply other threads:[~2014-06-12 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 10:36 Sanidhya Kashyap [this message]
2014-06-12 10:36 ` [Qemu-devel] [PATCH v3 1/7] enable sharing of the function between migration and bitmap dump Sanidhya Kashyap
2014-06-12 10:36 ` [Qemu-devel] [PATCH v3 2/7] RunState: added two new flags for bitmap dump and migration process Sanidhya Kashyap
2014-06-12 11:17 ` Sanidhya Kashyap
2014-06-12 10:36 ` [Qemu-devel] [PATCH v3 3/7] bitmap dump code via QAPI framework with runstates Sanidhya Kashyap
2014-06-12 10:36 ` [Qemu-devel] [PATCH v3 4/7] hmp interface for dirty bitmap dump Sanidhya Kashyap
2014-06-12 10:36 ` [Qemu-devel] [PATCH v3 5/7] cancel mechanism for an already running dump bitmap process Sanidhya Kashyap
2014-06-12 10:36 ` [Qemu-devel] [PATCH v3 6/7] set the frequency of the " Sanidhya Kashyap
2014-06-12 10:36 ` [Qemu-devel] [PATCH v3 7/7] python script for extracting bitmap from a binary file Sanidhya Kashyap
2014-06-12 11:47 ` [Qemu-devel] [PATCH v3 3/7][RESEND PATCH] bitmap dump code via QAPI framework with runstates 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=1402569400-12242-1-git-send-email-sanidhya.iiith@gmail.com \
--to=sanidhya.iiith@gmail.com \
--cc=dgilbert@redhat.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).