qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Fei Li <fli@suse.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC v2 5/5] migration: add more error handling for postcopy_ram_enable_notify
Date: Fri, 30 Nov 2018 09:49:49 +0000	[thread overview]
Message-ID: <20181130094949.GB2603@work-vm> (raw)
In-Reply-To: <20181129100340.13823-6-fli@suse.com>

* Fei Li (fli@suse.com) wrote:
> Call postcopy_ram_incoming_cleanup() to do the cleanup when
> postcopy_ram_enable_notify fails. Besides, report the error
> message when qemu_ram_foreach_migratable_block() fails.
> 
> Cc: Dr. David Alan Gilbert <dgilbert@redhat.com>
> Signed-off-by: Fei Li <fli@suse.com>

Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>

> ---
>  migration/postcopy-ram.c | 1 +
>  migration/savevm.c       | 1 +
>  2 files changed, 2 insertions(+)
> 
> diff --git a/migration/postcopy-ram.c b/migration/postcopy-ram.c
> index e5c02a32c5..fa09dba534 100644
> --- a/migration/postcopy-ram.c
> +++ b/migration/postcopy-ram.c
> @@ -1117,6 +1117,7 @@ int postcopy_ram_enable_notify(MigrationIncomingState *mis)
>  
>      /* Mark so that we get notified of accesses to unwritten areas */
>      if (qemu_ram_foreach_migratable_block(ram_block_enable_notify, mis)) {
> +        error_report("ram_block_enable_notify failed");
>          return -1;
>      }
>  
> diff --git a/migration/savevm.c b/migration/savevm.c
> index 9e45fb4f3f..d784e8aa40 100644
> --- a/migration/savevm.c
> +++ b/migration/savevm.c
> @@ -1729,6 +1729,7 @@ static int loadvm_postcopy_handle_listen(MigrationIncomingState *mis)
>       */
>      if (migrate_postcopy_ram()) {
>          if (postcopy_ram_enable_notify(mis)) {
> +            postcopy_ram_incoming_cleanup(mis);
>              return -1;
>          }
>      }
> -- 
> 2.13.7
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2018-11-30  9:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-29 10:03 [Qemu-devel] [PATCH RFC v2 0/5] fix some segmentation faults and migration issues Fei Li
2018-11-29 10:03 ` [Qemu-devel] [PATCH RFC v2 1/5] Fix segmentation fault when qemu_signal_init fails Fei Li
2018-11-29 12:49   ` Markus Armbruster
2018-11-30  3:29     ` Fei Li
2018-11-29 10:03 ` [Qemu-devel] [PATCH RFC v2 2/5] qemu_thread_join: fix segmentation fault Fei Li
2018-11-29 10:03 ` [Qemu-devel] [PATCH RFC v2 3/5] migration: fix the multifd code when receiving less channels Fei Li
2018-11-29 14:46   ` Philippe Mathieu-Daudé
2018-11-30  3:45     ` Fei Li
2018-12-06  6:31       ` Fei Li
2018-11-29 10:03 ` [Qemu-devel] [PATCH RFC v2 4/5] migration: remove unused &local_err parameter in multifd_save_cleanup Fei Li
2018-11-29 14:50   ` Philippe Mathieu-Daudé
2018-11-29 14:52     ` Philippe Mathieu-Daudé
2018-11-30  5:12     ` Fei Li
2018-11-29 10:03 ` [Qemu-devel] [PATCH RFC v2 5/5] migration: add more error handling for postcopy_ram_enable_notify Fei Li
2018-11-30  9:49   ` Dr. David Alan Gilbert [this message]
2018-11-29 14:20 ` [Qemu-devel] [PATCH for-3.1? RFC v2 0/5] fix some segmentation faults and migration issues Eric Blake
2018-11-30  6:15   ` Fei Li
2018-11-30 15:57     ` Eric Blake

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181130094949.GB2603@work-vm \
    --to=dgilbert@redhat.com \
    --cc=fli@suse.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).