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] [RFC PATCH v3 0/6] VMState testing
Date: Sat, 9 Aug 2014 02:26:29 -0400 [thread overview]
Message-ID: <1407565595-18861-1-git-send-email-sanidhya.iiith@gmail.com> (raw)
Hi,
The following patch introduce a mechanism to test the correctness of the
vmstate's information. This is achieved by saving the device states'
information to a memory buffer and then clearing the states, followed by
loading the data from the saved memory buffer.
v2 --> v3
* Made the devices list generic by removing the qdevified format. But, it only
supports the qdevified devices.
* Extended the SaveStateEntry for the VMstate testing purpose.
* Replaced DPRINTF with trace_##name functions.
* Squashed all of the hmp and qmp patches into one.
* Rectified some mistakes in the documentation of the hmp and qmp interface
explanations (the ones which I have introduced).
* Now, I am relying only on the devices that have been qdevified. I am not using
the qemu_system_reset() function for resetting the devices.
v1 --> v2:
* Added a list containing all the devices that have been qdevified and gets
registered with the SaveStateEntry.
* Have provided a way to use either qemu_system_reset functionality or my
own version of qdev entries untill all the devices have been qdevified.
This gives us the privilege to test any device we want.
* Rename some of the variables. I am very bad at naming convention, thanks to
community, specially Eric, I try to improve it with every version.
* On Eric's advice, I have separated all of the qmp and hmp interface patches.
* Changed the DPRINTF statements as required.
Dr. David Alan Gilbert (1):
QEMUSizedBuffer/QEMUFile
Sanidhya Kashyap (5):
VMState test: get information about the registered devices
VMstate test: basic VMState testing mechanism
VMState test: querying the vmstate testing process
VMState test: update period of vmstate testing process
VMState test: cancel mechanism for an already running vmstate testing
process
hmp-commands.hx | 49 +++++
hmp.c | 90 +++++++++
hmp.h | 5 +
include/migration/qemu-file.h | 27 +++
monitor.c | 14 ++
qapi-schema.json | 106 +++++++++++
qemu-file.c | 411 ++++++++++++++++++++++++++++++++++++++++++
qmp-commands.hx | 145 +++++++++++++++
savevm.c | 332 ++++++++++++++++++++++++++++++++++
trace-events | 2 +
10 files changed, 1181 insertions(+)
--
1.9.3
next reply other threads:[~2014-08-09 6:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 6:26 Sanidhya Kashyap [this message]
2014-08-09 6:26 ` [Qemu-devel] [RFC PATCH v3 1/6] QEMUSizedBuffer/QEMUFile Sanidhya Kashyap
2014-08-11 2:49 ` Gonglei (Arei)
2014-08-11 18:47 ` Dr. David Alan Gilbert
2014-08-11 19:16 ` Stefan Berger
2014-08-11 16:38 ` Eric Blake
2014-08-09 6:26 ` [Qemu-devel] [RFC PATCH v3 2/6] VMState test: get information about the registered devices Sanidhya Kashyap
2014-08-11 16:24 ` Eric Blake
2014-08-09 6:26 ` [Qemu-devel] [RFC PATCH v3 3/6] VMstate test: basic VMState testing mechanism Sanidhya Kashyap
2014-08-11 16:32 ` Eric Blake
2014-08-09 6:26 ` [Qemu-devel] [RFC PATCH v3 4/6] VMState test: querying the vmstate testing process Sanidhya Kashyap
2014-08-11 16:35 ` Eric Blake
2014-08-09 6:26 ` [Qemu-devel] [RFC PATCH v3 5/6] VMState test: update period of " Sanidhya Kashyap
2014-08-09 6:26 ` [Qemu-devel] [RFC PATCH v3 6/6] VMState test: cancel mechanism for an already running " 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=1407565595-18861-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).