History | View | Annotate | Download (30.2 kB)
vmstate: Add support for saving/loading bitmaps
Add support for saving/loading bitmap.h bitmaps in vmstate.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>Tested-by: Igor Mitsyanko <i.mitsyanko@samsung.com>Reviewed-by: Juan Quintela <quintela@redhat.com>
vmstate: add VMSTATE_TIMER_V
Also, for consistency with other occurrences, implement VMSTATE_TIMERas a special case of VMSTATE_TIMER_V rather than VMSTATE_TIMER_TEST.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
savevm: Use a struct to pass all handlers
This would make easier to add more operations in the next patches.
Signed-off-by: Juan Quintela <quintela@redhat.com>
savevm: Live migration handlers register the struct directly
Notice that the live migration users never unregister, so no problemabout freeing the ops structure.
savevm: remove SaveSetParamsHandler
It was used only once, just unfold.
savevm: remove SaveLiveStateHandler
savevm: Refactor cancel operation in its own operation
Intead of abusing stage with value -1.
savevm: introduce is_active method
Enable the creation of a method to tell migration if that section isactive and should be migrate. We use it for blk-migration, that isnormally not active. We don't create the method for RAM, as setupswithout RAM are very strange O:-)...
savevm: split save_live_setup from save_live_state
This patch splits stage 1 to its own function for both save_liveusers, ram and block. It is just a copy of the function, removing theparts of the other stages. Optimizations would came later.
savevm: split save_live into stage2 and stage3
We split it into 2 functions, foo_live_iterate, and foo_live_complete.At this point, we only remove the bits that are for the other stage,functionally this is equivalent to previous code.
Add MigrationParams structure
Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
Purge migration of (almost) everything to do with monitors
The Monitor object is passed back and forth within the migration/savevmcode so that it can print errors and progress to the user.
However, that approach assumes a HMP monitor, being completely invalid...
vmstate: extract declarations out of hw/hw.h