[Qemu-devel] [PATCH v6 1/6] generic function between migration and bitmap dump

2014-09-13 Thread Sanidhya Kashyap
Now, the counter variable is available to all the functions that will call qemu_bitmap_sync_range. I have tried to make the function along with the variables as generic as possible. Signed-off-by: Sanidhya Kashyap --- arch_init.c | 19 +++ include/exec/ram_addr.h

[Qemu-devel] [PATCH v6 6/6] BitmapLog: python script for extracting bitmap from a binary file

2014-09-13 Thread Sanidhya Kashyap
2 matrix dimension like 512 X 512 or 1024 X 512 etc for the dumping of the bitmap. But, I am still supporting the default square root based method of dimension selection. Signed-off-by: Sanidhya Kashyap --- scripts/extract-bitmap.py | 213 ++ 1 file

[Qemu-devel] [PATCH v6 3/6] BitmapLog: get the information about the parameters

2014-09-13 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- Removed acronyms, no functional change. hmp-commands.hx | 2 ++ hmp.c| 21 + hmp.h| 1 + monitor.c| 7 +++ qapi-schema.json | 28 qmp-commands.hx | 25

[Qemu-devel] [PATCH v6 5/6] BitmapLog: set the period of the dump bitmap process

2014-09-13 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- Removed acronyms, no functional change. hmp-commands.hx | 15 +++ hmp.c| 12 hmp.h| 1 + qapi-schema.json | 12 qmp-commands.hx | 24 savevm.c | 14

[Qemu-devel] [PATCH v6 0/6] Obtain dirty bitmap via VM logging

2014-09-13 Thread Sanidhya Kashyap
ffset. * 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

[Qemu-devel] [PATCH v6 2/6] BitmapLog: bitmap dump code

2014-09-13 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- No functional change, except: - naming convention i.e. QemuProcess has been changed to QemuDirtyBitmapUser. - rectified mistakes in documentation in qapi-schema.json. - removed acronyms hmp-commands.hx | 16 ++ hmp.c | 18

[Qemu-devel] [PATCH v6 4/6] BitmapLog: cancel mechanism for an already running dump bitmap process

2014-09-13 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- No functional change, except acronyms have been removed. Removed acronyms, no functional change. hmp-commands.hx | 14 ++ hmp.c| 5 + hmp.h| 1 + qapi-schema.json | 9 + qmp-commands.hx | 20

[Qemu-devel] [RFC PATCH v3 6/6] VMState test: cancel mechanism for an already running vmstate testing process

2014-08-08 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 14 ++ hmp.c| 6 ++ hmp.h| 1 + qapi-schema.json | 9 + qmp-commands.hx | 20 savevm.c | 16 ++-- 6 files changed, 64 insertions(+), 2 deletions

[Qemu-devel] [RFC PATCH v3 3/6] VMstate test: basic VMState testing mechanism

2014-08-08 Thread Sanidhya Kashyap
O the case pointed out by Juan does not exist. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 16 hmp.c| 17 hmp.h| 1 + qapi-schema.json | 22 ++ qmp-commands.hx | 33 savevm.c

[Qemu-devel] [RFC PATCH v3 0/6] VMState testing

2014-08-08 Thread Sanidhya Kashyap
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): QEMUSizedBuff

[Qemu-devel] [RFC PATCH v3 4/6] VMState test: querying the vmstate testing process

2014-08-08 Thread Sanidhya Kashyap
n the information about the running vmstate testing process. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 4 +++- hmp.c| 31 +++ hmp.h| 1 + monitor.c| 7 +++ qapi-schema.json | 37 +

[Qemu-devel] [RFC PATCH v3 5/6] VMState test: update period of vmstate testing process

2014-08-08 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 15 +++ hmp.c| 14 ++ hmp.h| 1 + qapi-schema.json | 12 qmp-commands.hx | 21 + savevm.c | 13 + 6 files changed, 76 insertions(+) diff

[Qemu-devel] [RFC PATCH v3 2/6] VMState test: get information about the registered devices

2014-08-08 Thread Sanidhya Kashyap
interface. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 2 ++ hmp.c| 23 +++ hmp.h| 1 + monitor.c| 7 +++ qapi-schema.json | 26 ++ qmp-commands.hx | 43 +++

[Qemu-devel] [RFC PATCH v3 1/6] QEMUSizedBuffer/QEMUFile

2014-08-08 Thread Sanidhya Kashyap
ers that can be written to or read from. Signed-off-by: Stefan Berger Signed-off-by: Joel Schopp Signed-off-by: Sanidhya Kashyap --- include/migration/qemu-file.h | 27 +++ qemu-file.c | 411 ++ 2 files changed, 438 insertions(+) diff

[Qemu-devel] [PATCH v5 5/6] BitmapLog: set the period of the dump bitmap process

2014-07-31 Thread Sanidhya Kashyap
No functional change except the variable name -- frequency has been modified to period. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 15 +++ hmp.c| 12 hmp.h| 1 + qapi-schema.json | 12 qmp-commands.hx | 24

[Qemu-devel] [PATCH v5 6/6] BitmapLog: python script for extracting bitmap from a binary file

2014-07-31 Thread Sanidhya Kashyap
ff-by: Sanidhya Kashyap --- scripts/extract-bitmap.py | 144 ++ 1 file changed, 144 insertions(+) create mode 100755 scripts/extract-bitmap.py diff --git a/scripts/extract-bitmap.py b/scripts/extract-bitmap.py new file mode 100755 index 000..94

[Qemu-devel] [PATCH v5 4/6] BitmapLog: cancel mechanism for an already running dump bitmap process

2014-07-31 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 14 ++ hmp.c| 5 + hmp.h| 1 + qapi-schema.json | 9 + qmp-commands.hx | 20 savevm.c | 14 ++ 6 files changed, 63 insertions(+) diff --git a/hmp

[Qemu-devel] [PATCH v5 3/6] BitmapLog: get the information about the parameters

2014-07-31 Thread Sanidhya Kashyap
No functional change except the variable name. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 2 ++ hmp.c| 19 +++ hmp.h| 1 + monitor.c| 7 +++ qapi-schema.json | 28 qmp-commands.hx | 25

[Qemu-devel] [PATCH v5 2/6] BitmapLog: bitmap dump code

2014-07-31 Thread Sanidhya Kashyap
en a device is hot plugged or hot unplugged. I have modified the variables name as: current-iteration: for the current iteration under process iterations: total iterations that will be done which is constant period: the delay in each iteration. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx

[Qemu-devel] [PATCH v5 1/6] generic function between migration and bitmap dump

2014-07-31 Thread Sanidhya Kashyap
I have modified the functions to be more generic i.e. I have used the counter variable which stores the required value. If the value of counter is 0, it means bitmap dump process whereas the value of 1 means migration. Signed-off-by: Sanidhya Kashyap --- arch_init.c | 21

[Qemu-devel] [PATCH v5 0/6] Obtain dirty bitmap via VM logging

2014-07-31 Thread Sanidhya Kashyap
Removed FILE pointer usage. * Dumping the data only in machine-readable format. * Tried to rectify mistakes of the previous version. Sanidhya Kashyap (6): generic function between migration and bitmap dump BitmapLog: bitmap dump code BitmapLog: get the information about the parameters Bit

Re: [Qemu-devel] [PATCH RFC v2 12/12] VMState test: hmp interface for cancel mechanism

2014-07-29 Thread Sanidhya Kashyap
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/29/2014 10:22 PM, Eric Blake wrote: > On 07/25/2014 09:39 AM, Sanidhya Kashyap wrote: >> Signed-off-by: Sanidhya Kashyap --- >> hmp-commands.hx | 14 ++ hmp.c | 6 ++ >> hmp.h | 1

Re: [Qemu-devel] [PATCH RFC v2 09/12] VMState test: update period of vmstate testing process

2014-07-29 Thread Sanidhya Kashyap
MSTATE_MIN_INTERVAL_MS, TEST_VMSTATE_MAX_INTERVAL_MS); + >> return; +} +v->period = period; +} > > This looks like it takes effect whether or not a vmstate test is > underway. Does this impact the default of the next vmstate test > to Yes > start, in the case where tha

Re: [Qemu-devel] [PATCH RFC v2 05/12] VMstate test: basic VMState testing mechanism

2014-07-29 Thread Sanidhya Kashyap
> > ok what are we doing here: > > > for(i=0; i< times; i++) { >. >f = qemu_bufopen("r", ..); >. >f = qemu_buf_get(f); >f = qemu_bufopen("w", ..) >... >qemu_fclose(f); > } > > > What I propose is switching to something like: > > f = qemu_bufopen("r", ..); > > for(i=0; i< times; i++) { > >qemu_buf_set_ro(f); >. >qemu_buf_set_rw(f) >... > } > qemu_fclose(f); > > > This makes qemu_bufopen() way simpler. Once there, my understanding is > that current code is leaking a QEMUBuffer each time that we call > qemu_bufopen("w", ...) > > Yup, I have missed qemu_fclose(f) before f = qemu_bufopen("r", ..); I'll correct it. Now, regarding the qemu_buf_set_ro and qemu_buf_set_rw, I guess, I'll have to rewind the pointer, for which I have to get some idea before doing it, or extend the QEMUFile code for memory buffer. -- - Sanidhya Kashyap

Re: [Qemu-devel] [PATCH RFC v2 03/12] VMState test: query command to extract the qdevified device names

2014-07-29 Thread Sanidhya Kashyap
like: > > "devices": [ [ "device": [ "name": "kvm-tpr-opt", "version", 15]]], ...] > > Or somesuch? > That is possible. Do you want any other information to be printed? -- - Sanidhya Kashyap

[Qemu-devel] [PATCH RFC v2 09/12] VMState test: update period of vmstate testing process

2014-07-25 Thread Sanidhya Kashyap
No particular change, except variable name. Since I am not modifying other variables, so I have not made the command generic. Signed-off-by: Sanidhya Kashyap --- qapi-schema.json | 12 qmp-commands.hx | 23 +++ savevm.c | 13 + 3 files

[Qemu-devel] [PATCH RFC v2 12/12] VMState test: hmp interface for cancel mechanism

2014-07-25 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 14 ++ hmp.c | 6 ++ hmp.h | 1 + 3 files changed, 21 insertions(+) diff --git a/hmp-commands.hx b/hmp-commands.hx index 6d15184..fe224fc 100644 --- a/hmp-commands.hx +++ b/hmp-commands.hx @@ -1822,6

[Qemu-devel] [PATCH RFC v2 08/12] VMState test: hmp interface for querying the vmstate testing process

2014-07-25 Thread Sanidhya Kashyap
Added a hmp interface for providing the information about the testing process. I have used the underscore as a separater on Eric's advice. But, I have found some of the commands having hyphen. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 2 ++ hmp.c

[Qemu-devel] [PATCH RFC v2 07/12] VMState test: qmp interface for querying the vmstate testing process

2014-07-25 Thread Sanidhya Kashyap
This patch provides the information about an already executing testing process. I have modified the qmp command to query-test-vmstates from test-vmstates-get-info. Signed-off-by: Sanidhya Kashyap --- qapi-schema.json | 34 ++ qmp-commands.hx | 25

[Qemu-devel] [PATCH RFC v2 11/12] VMState test: cancel mechanism for an already running vmstate testing process

2014-07-25 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- qapi-schema.json | 9 + qmp-commands.hx | 19 +++ savevm.c | 16 ++-- 3 files changed, 42 insertions(+), 2 deletions(-) diff --git a/qapi-schema.json b/qapi-schema.json index 13e922e..91f1672 100644 --- a/qapi

[Qemu-devel] [PATCH RFC v2 06/12] VMState test: hmp interface for vmstate testing

2014-07-25 Thread Sanidhya Kashyap
I have added the hmp interface for vmstate testing. Currently, the patch does not support the qdev list, since I could not figure out how to the pass the VMStatesQdevDevices struct which can be parsed and used. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 15 +++ hmp.c

[Qemu-devel] [PATCH RFC v2 10/12] VMState test: hmp interface for period update

2014-07-25 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 15 +++ hmp.c | 14 ++ hmp.h | 1 + 3 files changed, 30 insertions(+) diff --git a/hmp-commands.hx b/hmp-commands.hx index c1dc6a2..6d15184 100644 --- a/hmp-commands.hx +++ b/hmp-commands.hx

[Qemu-devel] [PATCH RFC v2 02/12] reset handler for qdevified devices

2014-07-25 Thread Sanidhya Kashyap
grateful if anyone can give some pointers on this. Signed-off-by: Sanidhya Kashyap --- savevm.c | 30 ++ 1 file changed, 30 insertions(+) diff --git a/savevm.c b/savevm.c index e19ae0a..0255fa0 100644 --- a/savevm.c +++ b/savevm.c @@ -503,12 +503,29 @@ void

[Qemu-devel] [PATCH RFC v2 04/12] VMState test: hmp interface for showing qdevified devices

2014-07-25 Thread Sanidhya Kashyap
This patch provides the hmp interface for qdevified devices list. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 2 ++ hmp.c | 21 + hmp.h | 1 + monitor.c | 7 +++ 4 files changed, 31 insertions(+) diff --git a/hmp-commands.hx b/hmp

[Qemu-devel] [PATCH RFC v2 05/12] VMstate test: basic VMState testing mechanism

2014-07-25 Thread Sanidhya Kashyap
documentation. Signed-off-by: Sanidhya Kashyap --- qapi-schema.json | 26 ++ qmp-commands.hx | 37 savevm.c | 251 +++ 3 files changed, 314 insertions(+) diff --git a/qapi-schema.json b/qapi-schema.json index 996e6b5..ec48977

[Qemu-devel] [PATCH RFC v2 03/12] VMState test: query command to extract the qdevified device names

2014-07-25 Thread Sanidhya Kashyap
I have provided a qmp interface for getting the list of qdevified devices that have been registered with SaveVMHandlers. Signed-off-by: Sanidhya Kashyap --- qapi-schema.json | 22 ++ qmp-commands.hx | 25 + savevm.c | 34

[Qemu-devel] [PATCH RFC v2 01/12] QEMUSizedBuffer/QEMUFile

2014-07-25 Thread Sanidhya Kashyap
From: "Dr. David Alan Gilbert" Stefan Berger's to create a QEMUFile that goes to a memory buffer; from: http://lists.gnu.org/archive/html/qemu-devel/2013-03/msg05036.html Using the QEMUFile interface, this patch adds support functions for operating on in-memory sized buffers that can be written

[Qemu-devel] [PATCH RFC v2 00/12] VMState testing

2014-07-25 Thread Sanidhya Kashyap
id Alan Gilbert (1): QEMUSizedBuffer/QEMUFile Sanidhya Kashyap (11): reset handler for qdevified devices VMState test: query command to extract the qdevified device names VMState test: hmp interface for showing qdevified devices VMstate test: basic VMState testing mechanism VMState t

Re: [Qemu-devel] [RFC PATCH v1 4/5] VMState test: set the frequency of the vmstate testing process

2014-07-18 Thread Sanidhya Kashyap
"type":"int", "value":100 }, { "name":"other", > "type":"...", "value":... } ]} > > Well, I have some issues about the implementation of the list which is associated with the set-tuning one. Any patch il

Re: [Qemu-devel] [PATCH v4 3/8] BitmapLog: bitmap dump code via QAPI framework with runstates

2014-07-18 Thread Sanidhya Kashyap
gt; +logging_state_set_status(b, LOG_BITMAP_STATE_ERROR, >> +LOG_BITMAP_STATE_COMPLETED); >> +} >> +return; >> +} > > I didn't really see the point of this at first, but I guess > it always moves to 'COMPLETED' unless you're already at completed > or in NONE; but then perhaps: > > int s = b->state; > switch (s) { > case LOG_BITMAP_STATE_ACTIVE: > case LOG_BITMAP_STATE_CANCELING: > case LOG_BITMAP_STATE_ERROR: >logging_state_set_status(b, s, >LOG_BITMAP_STATE_COMPLETED); >return; >} >return; > > would be more obvious (note I only read the state once) > Yup, will save some code and reduce confusion. -- - Sanidhya Kashyap

Re: [Qemu-devel] [PATCH v4 3/8] BitmapLog: bitmap dump code via QAPI framework with runstates

2014-07-18 Thread Sanidhya Kashyap
nge the misleading name and will specify this point in the documentation as well as in the code. -- - Sanidhya Kashyap

Re: [Qemu-devel] [PATCH v4 2/8] RunState: added two new flags for bitmap dump and migration process

2014-07-18 Thread Sanidhya Kashyap
hen the dump-bitmap process will terminate. Well, that is my thinking and it can either be redundant or useless. I have no idea what will happen to the older libvirt. :-/ - -- - - Sanidhya Kashyap -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://

Re: [Qemu-devel] [PATCH v4 5/8] BitmapLog: cancel mechanism for an already running dump bitmap process

2014-07-18 Thread Sanidhya Kashyap
log-dirty-bitmap-cancel", > > HMP commands still use _ in their names; it's only QMP where we > prefer dash. > I didn't notice. Will change it. - - Sanidhya Kashyap -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Usin

Re: [Qemu-devel] [PATCH v4 7/8] BitmapLog: get the information about the parameters

2014-07-18 Thread Sanidhya Kashyap
ich led to my question > about semantics), it might be nicer to just mention here that the > information is returned as a BitmapLogStateInfo and be done with it > (the user can go look up the documentation of that struct). > Will do that. - -- - - Sanidhya

Re: [Qemu-devel] [PATCH v4 0/8] Obtain dirty bitmap via VM logging

2014-07-18 Thread Sanidhya Kashyap
n allow us to execute only one of the processes - either migration or bitmap dump. One very basic approach that I have thought is about using a global variable but don't know whether that is a good option or not. Any other alternative is welcomed. - Sanidhya Kashyap

[Qemu-devel] [PATCH v4 7/8] BitmapLog: get the information about the parameters

2014-07-17 Thread Sanidhya Kashyap
modify the other values except frequency, so that is why I have not added the generic set-tuning interface. If required, I will add it. Signed-off-by: Sanidhya Kashyap --- qapi-schema.json | 31 +++ qmp-commands.hx | 24 savevm.c | 26

[Qemu-devel] [PATCH v4 8/8] BitmapLog: python script for extracting bitmap from a binary file

2014-07-17 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- scripts/extract-bitmap.py | 97 +++ 1 file changed, 97 insertions(+) create mode 100755 scripts/extract-bitmap.py diff --git a/scripts/extract-bitmap.py b/scripts/extract-bitmap.py new file mode 100755 index

[Qemu-devel] [PATCH v4 6/8] BitmapLog: set the frequency of the dump bitmap process

2014-07-17 Thread Sanidhya Kashyap
Rectified the example mistake in qmp-commands.hx. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 15 +++ hmp.c| 12 hmp.h| 1 + qapi-schema.json | 13 + qmp-commands.hx | 24 savevm.c | 14

[Qemu-devel] [PATCH v4 5/8] BitmapLog: cancel mechanism for an already running dump bitmap process

2014-07-17 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 14 ++ hmp.c| 5 + hmp.h| 1 + qapi-schema.json | 8 qmp-commands.hx | 21 + savevm.c | 19 +++ 6 files changed, 68 insertions(+) diff --git a

[Qemu-devel] [PATCH v4 4/8] BitmapLog: hmp interface for dirty bitmap dump

2014-07-17 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 16 hmp.c | 16 hmp.h | 1 + 3 files changed, 33 insertions(+) diff --git a/hmp-commands.hx b/hmp-commands.hx index d0943b1..575df78 100644 --- a/hmp-commands.hx +++ b/hmp-commands.hx

[Qemu-devel] [PATCH v4 3/8] BitmapLog: bitmap dump code via QAPI framework with runstates

2014-07-17 Thread Sanidhya Kashyap
Reformatted the code and added the functionality of dumping the blocks' info which can be read by the user when required. I have also made the block name length global. Some minor modification to the structure which is now storing all the information. Signed-off-by: Sanidhya Kashyap --- in

[Qemu-devel] [PATCH v4 2/8] RunState: added two new flags for bitmap dump and migration process

2014-07-17 Thread Sanidhya Kashyap
Changed those files that were directly using the RUN_STATE_RUNNING flag. Now, they have been replaced by the runstate_is_running() function. Signed-off-by: Sanidhya Kashyap --- hw/usb/hcd-ehci.c | 2 +- hw/usb/redirect.c | 6 +++--- qapi-schema.json | 7 ++- vl.c | 29

[Qemu-devel] [PATCH v4 1/8] enable sharing of the function between migration and bitmap dump

2014-07-17 Thread Sanidhya Kashyap
Added prefix qemu_ to the function as pointed out by Juan. Signed-off-by: Sanidhya Kashyap --- arch_init.c | 19 +++ include/exec/ram_addr.h | 4 2 files changed, 15 insertions(+), 8 deletions(-) diff --git a/arch_init.c b/arch_init.c index 8ddaf35..9ac4602

[Qemu-devel] [PATCH v4 0/8] Obtain dirty bitmap via VM logging

2014-07-17 Thread Sanidhya Kashyap
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 (8): enable sharing of the function between migrat

Re: [Qemu-devel] [PATCH 00/46] Postcopy implementation

2014-07-10 Thread Sanidhya Kashyap
>> The single precopy lazy pass would consist of clearing the dirty >> bitmap, starting precopy, then if any page is found dirty by the time >> precopy tries to send it, we skip it. We only send those pages in >> precopy that haven't been modified yet by the time we reach them in >> precopy. >> >>

[Qemu-devel] [RFC PATCH v1 5/5] VMState test: cancel mechanism for an already running vmstate testing process

2014-07-07 Thread Sanidhya Kashyap
This patch helps in cancelling an already executing vmstate testing process. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 14 ++ hmp.c| 6 ++ hmp.h| 1 + qapi-schema.json | 9 + qmp-commands.hx | 20 savevm.c

[Qemu-devel] [RFC PATCH v1 4/5] VMState test: set the frequency of the vmstate testing process

2014-07-07 Thread Sanidhya Kashyap
This patch introduces the mechanism to update the sleep interval - sinterval. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 15 +++ hmp.c| 14 ++ hmp.h| 1 + qapi-schema.json | 10 ++ qmp-commands.hx | 22

[Qemu-devel] [RFC PATCH v1 2/5] VMState test: basic vmstate testing mechanism

2014-07-07 Thread Sanidhya Kashyap
e the qdevified device tree to reset the functions. As of now, I am providing DPRINTF to know about the amount of time spend in saving and loading the data from the buffer. If there is any other way that should be used to print the stats, then please do let me know. Signed-off-by: Sanidhya Kashyap ---

[Qemu-devel] [RFC PATCH v1 3/5] VMState test: hmp interface for vmstate testing

2014-07-07 Thread Sanidhya Kashyap
Added hmp interface. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 15 +++ hmp.c | 14 ++ hmp.h | 1 + 3 files changed, 30 insertions(+) diff --git a/hmp-commands.hx b/hmp-commands.hx index d0943b1..c492f3f 100644 --- a/hmp-commands.hx +++ b

[Qemu-devel] [RFC PATCH v1 1/5] QEMUSizedBuffer/QEMUFile

2014-07-07 Thread Sanidhya Kashyap
From: "Dr. David Alan Gilbert" Using the patch of Stefan Berger for memory buffer based QEMUFile. http://lists.gnu.org/archive/html/qemu-devel/2013-03/msg05036.html In the words of David: """ Using the QEMUFile interface, this patch adds support functions for operating on in-memory sized buffe

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

2014-07-07 Thread Sanidhya Kashyap
nterval 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 te

[Qemu-devel] [PATCH v3 3/7][RESEND PATCH] bitmap dump code via QAPI framework with runstates

2014-06-12 Thread Sanidhya Kashyap
Reformatted the code and added the functionality of dumping the blocks' info which can be read by the user when required. I have also made the block name length global. Signed-off-by: Sanidhya Kashyap --- include/exec/cpu-all.h | 3 +- migration.c| 7 ++ qapi-schema

Re: [Qemu-devel] [PATCH v3 2/7] RunState: added two new flags for bitmap dump and migration process

2014-06-12 Thread Sanidhya Kashyap
> int runstate_is_running(void) > { > -return runstate_check(RUN_STATE_RUNNING); > +return (runstate_check(RUN_STATE_RUNNING) || > +runstate_check(RUN_STATE_MIGRATE) || > +runstate_check(RUN_STATE_DUMP_BITMAP)); > } Forgot to apply the checkpatch script. The retu

[Qemu-devel] [PATCH v3 6/7] set the frequency of the dump bitmap process

2014-06-12 Thread Sanidhya Kashyap
No, particular change except the function name changed - value_in_range(). Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 15 +++ hmp.c| 12 hmp.h| 1 + qapi-schema.json | 11 +++ qmp-commands.hx | 24

[Qemu-devel] [PATCH v3 5/7] cancel mechanism for an already running dump bitmap process

2014-06-12 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 14 ++ hmp.c| 5 + hmp.h| 1 + qapi-schema.json | 8 qmp-commands.hx | 20 savevm.c | 19 +++ 6 files changed, 67 insertions(+) diff --git a

[Qemu-devel] [PATCH v3 7/7] python script for extracting bitmap from a binary file

2014-06-12 Thread Sanidhya Kashyap
which acts as a marker identifying as the end of that bitmap. If the 'M' is missing while reading the file, then dump is incomplete. Signed-off-by: Sanidhya Kashyap --- scripts/extract-bitmap.py | 97 +++ 1 file changed, 97 insertions(+) c

[Qemu-devel] [PATCH v3 4/7] hmp interface for dirty bitmap dump

2014-06-12 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 16 hmp.c | 16 hmp.h | 1 + 3 files changed, 33 insertions(+) diff --git a/hmp-commands.hx b/hmp-commands.hx index 5f1a677..cccd53e 100644 --- a/hmp-commands.hx +++ b/hmp-commands.hx

[Qemu-devel] [PATCH v3 2/7] RunState: added two new flags for bitmap dump and migration process

2014-06-12 Thread Sanidhya Kashyap
Changed those files that were directly using the RUN_STATE_RUNNING flag. Now, they have been replaced by the runstate_is_running() function. Signed-off-by: Sanidhya Kashyap --- hw/usb/hcd-ehci.c | 2 +- hw/usb/redirect.c | 6 +++--- qapi-schema.json | 7 ++- vl.c | 29

[Qemu-devel] [PATCH v3 0/7] Obtain dirty bitmap via VM logging

2014-06-12 Thread Sanidhya Kashyap
emoved 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 du

[Qemu-devel] [PATCH v3 3/7] bitmap dump code via QAPI framework with runstates

2014-06-12 Thread Sanidhya Kashyap
Reformatted the code and added the functionality of dumping the blocks' info which can be read by the user when required. I have also made the block name length global. Signed-off-by: Sanidhya Kashyap --- include/exec/cpu-all.h | 3 +- migration.c| 7 ++ qapi-schema

[Qemu-devel] [PATCH v3 1/7] enable sharing of the function between migration and bitmap dump

2014-06-12 Thread Sanidhya Kashyap
Added prefix qemu_ to the function as pointed out by Juan. Signed-off-by: Sanidhya Kashyap --- arch_init.c | 19 +++ include/exec/ram_addr.h | 4 2 files changed, 15 insertions(+), 8 deletions(-) diff --git a/arch_init.c b/arch_init.c index 23044c1..2fec98b

Re: [Qemu-devel] [PATCH v2 1/8] enable sharing of the function between migration and bitmap dump

2014-06-04 Thread Sanidhya Kashyap
trick? > > > Later, Juan. Got it! -- Sanidhya Kashyap

Re: [Qemu-devel] [PATCH v2 1/8] enable sharing of the function between migration and bitmap dump

2014-06-04 Thread Sanidhya Kashyap
> > Exporting a function without a prefix could be dangerous. > > Later, Juan. Any particular solution, as the function is being used at two places. -- Sanidhya Kashyap

[Qemu-devel] [PATCH v2 5/8] hmp interface for dirty bitmap dump

2014-06-04 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 16 hmp.c | 16 hmp.h | 1 + 3 files changed, 33 insertions(+) diff --git a/hmp-commands.hx b/hmp-commands.hx index 2e462c0..1665587 100644 --- a/hmp-commands.hx +++ b/hmp-commands.hx

[Qemu-devel] [PATCH v2 6/8] cancel mechanism for an already running dump bitmap process

2014-06-04 Thread Sanidhya Kashyap
No particular functional changes. Rectified some previous mistakes. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 14 ++ hmp.c| 5 + hmp.h| 1 + qapi-schema.json | 8 qmp-commands.hx | 20 savevm.c | 19

[Qemu-devel] [PATCH v2 1/8] enable sharing of the function between migration and bitmap dump

2014-06-03 Thread Sanidhya Kashyap
As advised by Eric, I have enabled sharing of the function between of the function that syncs the dirty bitmap obtained via kvm ioctl. I have tried to make the least changes to the functions by concentrating only on the function definitions. Signed-off-by: Sanidhya Kashyap --- arch_init.c

[Qemu-devel] [PATCH v2 7/8] set the frequency of the dump bitmap process

2014-06-03 Thread Sanidhya Kashyap
No particular functional change. Corrected some mistakes. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 15 +++ hmp.c| 12 hmp.h| 1 + qapi-schema.json | 10 ++ qmp-commands.hx | 23 +++ savevm.c

[Qemu-devel] [PATCH v2 4/8] bitmap dump process with runstates

2014-06-03 Thread Sanidhya Kashyap
interface as the current_run_state variable is not updated. Any thoughts on that? Do I need to make the changes there as well or is there any simple way to do it? Signed-off-by: Sanidhya Kashyap --- migration.c | 7 +++ savevm.c| 26 +++--- 2 files changed, 26

[Qemu-devel] [PATCH v2 3/8] RunState: added two new flags for bitmap dump and migration process

2014-06-03 Thread Sanidhya Kashyap
but I have tried to cover what I thought is necessary). Signed-off-by: Sanidhya Kashyap --- qapi-schema.json | 7 ++- vl.c | 29 - 2 files changed, 34 insertions(+), 2 deletions(-) diff --git a/qapi-schema.json b/qapi-schema.json index 17e5147..29

[Qemu-devel] [PATCH v2 8/8] python script for extracting bitmap from a binary file

2014-06-03 Thread Sanidhya Kashyap
No particular functional change. This file does not need to be included in the Makefile as it will be only useful once the user has generated the bitmap file via bitmap dump process. Signed-off-by: Sanidhya Kashyap --- scripts/extract-bitmap.py | 64

[Qemu-devel] [PATCH v2 2/8] bitmap dump code via QAPI framework

2014-06-03 Thread Sanidhya Kashyap
close with qemu_open / qemu_close. 4) Removed text format, output only in machine-readable format. 5) Defined constants. Signed-off-by: Sanidhya Kashyap --- qapi-schema.json | 17 qmp-commands.hx | 33 savevm.c | 246 ++

[Qemu-devel] [PATCH v2 0/8] Obtain dirty bitmap via VM logging

2014-06-03 Thread Sanidhya Kashyap
ion 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 (8): enable sharing of the function between migration and bitmap dump bitmap dump code via Q

[Qemu-devel] [PATCH 2/8] bitmap dump code via QAPI framework

2014-05-26 Thread Sanidhya Kashyap
close with qemu_open / qemu_close. 4) Removed text format, output only in machine-readable format. 5) Defined constants. Signed-off-by: Sanidhya Kashyap --- qapi-schema.json | 17 qmp-commands.hx | 33 savevm.c | 246 ++

[Qemu-devel] [PATCH 3/8] RunState: added two new flags for bitmap dump and migration process

2014-05-25 Thread Sanidhya Kashyap
but I have tried to cover what I thought is necessary). Signed-off-by: Sanidhya Kashyap --- qapi-schema.json | 7 ++- vl.c | 29 - 2 files changed, 34 insertions(+), 2 deletions(-) diff --git a/qapi-schema.json b/qapi-schema.json index 17e5147..29

[Qemu-devel] [PATCH 7/8] set the frequency of the dump bitmap process

2014-05-25 Thread Sanidhya Kashyap
No particular functional change. Corrected some mistakes. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 15 +++ hmp.c| 12 hmp.h| 1 + qapi-schema.json | 10 ++ qmp-commands.hx | 23 +++ savevm.c

[Qemu-devel] [PATCH 6/8] cancel mechanism for an already running dump bitmap process

2014-05-25 Thread Sanidhya Kashyap
No particular functional changes. Rectified some previous mistakes. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 14 ++ hmp.c| 5 + hmp.h| 1 + qapi-schema.json | 8 qmp-commands.hx | 20 savevm.c | 19

[Qemu-devel] [PATCH 5/8] hmp interface for dirty bitmap dump

2014-05-25 Thread Sanidhya Kashyap
Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 16 hmp.c | 16 hmp.h | 1 + 3 files changed, 33 insertions(+) diff --git a/hmp-commands.hx b/hmp-commands.hx index 2e462c0..1665587 100644 --- a/hmp-commands.hx +++ b/hmp-commands.hx

[Qemu-devel] [PATCH 4/8] bitmap dump process with runstates

2014-05-25 Thread Sanidhya Kashyap
interface as the current_run_state variable is not updated. Any thoughts on that? Do I need to make the changes there as well or is there any simple way to do it? Signed-off-by: Sanidhya Kashyap --- migration.c | 7 +++ savevm.c| 26 +++--- 2 files changed, 26

[Qemu-devel] [PATCH 8/8] python script for extracting bitmap from a binary file

2014-05-25 Thread Sanidhya Kashyap
No particular functional change. This file does not need to be included in the Makefile as it will be only useful once the user has generated the bitmap file via bitmap dump process. Signed-off-by: Sanidhya Kashyap --- scripts/extract-bitmap.py | 64

[Qemu-devel] [PATCH 1/8] enable sharing of the function between migration and bitmap dump

2014-05-25 Thread Sanidhya Kashyap
As advised by Eric, I have enabled sharing of the function between of the function that syncs the dirty bitmap obtained via kvm ioctl. I have tried to make the least changes to the functions by concentrating only on the function definitions. Signed-off-by: Sanidhya Kashyap --- arch_init.c

[Qemu-devel] [PATCH 0/8] Obtain dirty bitmap via VM logging

2014-05-25 Thread Sanidhya Kashyap
ion 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 Q

Re: [Qemu-devel] [PATCH 0/6] Obtain dirty bitmap via VM logging

2014-05-22 Thread Sanidhya Kashyap
to RUN_STATE_MIGRATE when > migrate. > BTW, it is not your patches problem. > Then, I'll go ahead and implement this part using two flags in my second version of the patches. > cc: Juan > > Best regards > ChenLiang > -- Sanidhya Kashyap

Re: [Qemu-devel] [PATCH 0/6] Obtain dirty bitmap via VM logging

2014-05-22 Thread Sanidhya Kashyap
On Wed, May 21, 2014 at 12:15 PM, ChenLiang wrote: > On 2014/5/21 12:56, Sanidhya Kashyap wrote: > >> On Wed, May 21, 2014 at 9:43 AM, ChenLiang wrote: >>> Hi, >>> Nice job. We should avoid running migration_thread and >>> bitmap_logging_thread simultane

Re: [Qemu-devel] [PATCH 0/6] Obtain dirty bitmap via VM logging

2014-05-20 Thread Sanidhya Kashyap
tml ). I can directly use the DIRTY_MEMORY_MIGRATION flag. What is your suggestion? -- Sanidhya Kashyap

Re: [Qemu-devel] [PATCH 0/6] Obtain dirty bitmap via VM logging

2014-05-20 Thread Sanidhya Kashyap
On Wed, May 21, 2014 at 9:43 AM, ChenLiang wrote: > Hi, > Nice job. We should avoid running migration_thread and bitmap_logging_thread > simultaneously. > Any particular suggestion to avoid running simultaneous execution of the threads? -- Sanidhya

Re: [Qemu-devel] [PATCH 6/6] python script for extracting bitmap from a binary file

2014-05-20 Thread Sanidhya Kashyap
>>> Signed-off-by: Sanidhya Kashyap >>> --- >>> scripts/extract-bitmap.py | 68 >>> +++ >>> 1 file changed, 68 insertions(+) >>> create mode 100755 scripts/extract-bitmap.py > > Does this

Re: [Qemu-devel] [PATCH 2/6] bitmap dump code via QAPI framework

2014-05-20 Thread Sanidhya Kashyap
>> +#define QERR_LOG_DIRTY_BITMAP_ACTIVE \ >> +ERROR_CLASS_GENERIC_ERROR, "Dirty bitmap dump already in progress" >> + > > Please don't add new ERROR_CLASS macros. Instead, just use error_setg() > and directly output the error message at the call site that produces the > error. > will keep in

[Qemu-devel] [PATCH 3/6] hmp interface for dirty bitmap dump

2014-05-20 Thread Sanidhya Kashyap
Added the log-dirty-bitmap or ldb hmp interface. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 17 + hmp.c | 19 +++ hmp.h | 1 + 3 files changed, 37 insertions(+) diff --git a/hmp-commands.hx b/hmp-commands.hx index 8971f1b..032a320

[Qemu-devel] [PATCH 6/6] python script for extracting bitmap from a binary file

2014-05-20 Thread Sanidhya Kashyap
This script extracts the bitmap only from a binary file. It takes only a single input as file. This will be useful to users for exploring the writable working set for the VM. Signed-off-by: Sanidhya Kashyap --- scripts/extract-bitmap.py | 68 +++ 1

[Qemu-devel] [PATCH 5/6] set the frequency of the dump bitmap process

2014-05-20 Thread Sanidhya Kashyap
This patch introduces both qmp and hmp (log-dirty-bitmap-set-frequency) interface to update the value of the frequency. Signed-off-by: Sanidhya Kashyap --- hmp-commands.hx | 15 +++ hmp.c| 12 hmp.h| 1 + qapi-schema.json | 8 qmp

  1   2   >