diff options
| author | Peter Xu <peterx@redhat.com> | 2018-05-02 18:47:20 +0800 |
|---|---|---|
| committer | Juan Quintela <quintela@redhat.com> | 2018-05-15 20:24:27 +0200 |
| commit | b411b844fb2e038c6ba92fd50fed3213a27c6445 (patch) | |
| tree | 62a1cf5d1b36d66bdc16d97a93d50315e295077f /migration/trace-events | |
| parent | b23c2ade250718fe77b51e116f95f3c34c8a4c24 (diff) | |
| download | qemu-b411b844fb2e038c6ba92fd50fed3213a27c6445.zip qemu-b411b844fb2e038c6ba92fd50fed3213a27c6445.tar.gz qemu-b411b844fb2e038c6ba92fd50fed3213a27c6445.tar.bz2 | |
migration: allow dst vm pause on postcopy
When there is IO error on the incoming channel (e.g., network down),
instead of bailing out immediately, we allow the dst vm to switch to the
new POSTCOPY_PAUSE state. Currently it is still simple - it waits the
new semaphore, until someone poke it for another attempt.
One note is that here on ram loading thread we cannot detect the
POSTCOPY_ACTIVE state, but we need to detect the more specific
POSTCOPY_INCOMING_RUNNING state, to make sure we have already loaded all
the device states.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20180502104740.12123-5-peterx@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Diffstat (limited to 'migration/trace-events')
| -rw-r--r-- | migration/trace-events | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/migration/trace-events b/migration/trace-events index 409b4b8..e23ec01 100644 --- a/migration/trace-events +++ b/migration/trace-events @@ -100,6 +100,8 @@ open_return_path_on_source(void) "" open_return_path_on_source_continue(void) "" postcopy_start(void) "" postcopy_pause_continued(void) "" +postcopy_pause_incoming(void) "" +postcopy_pause_incoming_continued(void) "" postcopy_start_set_run(void) "" source_return_path_thread_bad_end(void) "" source_return_path_thread_end(void) "" |