qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [RFC PATCH v1 0/5] VMState testing


From: Sanidhya Kashyap
Subject: [Qemu-devel] [RFC PATCH v1 0/5] VMState testing
Date: Mon, 7 Jul 2014 22:47:59 +0530

Hi,

This patch series introduces a mechanism to test the vmstates' information.
Currently, this is achieved by saving the device states' information to
a memory buffer - an abstraction provided by QEMUFile pointer (David's patch)
and then clearing the states followed by loading the data from the buffer.
Currently, this is just a basic implementation in which one cannot test a
particular device - due to the issues in the reset functionality. In the next
version of the patch, I will try to work on this issue so that the vmstate
checking is possible for every device. This will help the users to enable
checking of a device at the time of saving and loading of its state.

I have tried to provide the both of the hmp and qmp commands interface to dump
and load the vmstates. Besides this, one can either cancel an already running
testing process or update the required sleep interval between iteration.

With these patches, I haven't found any bug in the device states. I wish I am
on the right track.


Dr. David Alan Gilbert (1):
  QEMUSizedBuffer/QEMUFile

Sanidhya Kashyap (4):
  VMState test: basic vmstate testing mechanism
  VMState test: hmp interface for vmstate testing
  VMState test: set the frequency of the vmstate testing process
  VMState test: cancel mechanism for an already running vmstate testing
    process

 hmp-commands.hx               |  44 +++++
 hmp.c                         |  34 ++++
 hmp.h                         |   3 +
 include/migration/qemu-file.h |  27 +++
 qapi-schema.json              |  31 ++++
 qemu-file.c                   | 411 ++++++++++++++++++++++++++++++++++++++++++
 qmp-commands.hx               |  70 +++++++
 savevm.c                      | 174 ++++++++++++++++++
 8 files changed, 794 insertions(+)

-- 
1.9.3




reply via email to

[Prev in Thread] Current Thread [Next in Thread]