Hi At the end, Daved asked for a couple of things on previous series.
[v2] - Ensure that we start in NONE even after failed/canceled migration - move printf's to traces - make sure that we can migrate the new states like guest-panicked (not sure if it is a good idea to enable migrate a guest-panicked, but it is not this series the place to forbid it) - address all comments from Dave and Eric. Please, review. [v1] As the beggining of both series have been accepted, I merged both here. Changes: - answered all comments on list and applied suggested changes - Use migrate_set_state() consistently - we were misusing atomic_cmpxchg(), it didn't matter until now because we were missing only traces, but it showed with events missing. - Reorganized how the migration events are generated, now only on migrate_set_state. Please review. Juan Quintela (12): runstate: Add runstate store runstate: migration allows more transitions now migration: create new section to store global state global_state: Make section optional vmstate: Create optional sections migration: Add configuration section migration: Use cmpxchg correctly migration: ensure we start in NONE state migration: Use always helper to set state migration: No need to call trace_migrate_set_state() migration: create migration event migration: Add migration events on target side docs/qmp/qmp-events.txt | 14 ++++ hw/i386/pc_piix.c | 2 + hw/i386/pc_q35.c | 2 + include/migration/migration.h | 4 ++ include/migration/vmstate.h | 2 + include/sysemu/sysemu.h | 1 + migration/migration.c | 157 ++++++++++++++++++++++++++++++++++++++---- migration/savevm.c | 69 +++++++++++++++++++ migration/vmstate.c | 11 +++ qapi/event.json | 12 ++++ trace-events | 4 ++ vl.c | 21 +++++- 12 files changed, 283 insertions(+), 16 deletions(-) -- 2.4.3