All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: guangrong.xiao@gmail.com
Cc: kvm@vger.kernel.org, mst@redhat.com, mtosatti@redhat.com,
	Xiao Guangrong <xiaoguangrong@tencent.com>,
	dgilbert@redhat.com, qemu-devel@nongnu.org, wei.w.wang@intel.com,
	jiang.biao2@zte.com.cn, pbonzini@redhat.com
Subject: Re: [PATCH v3 08/10] migration: handle the error condition properly
Date: Wed, 8 Aug 2018 13:08:46 +0800	[thread overview]
Message-ID: <20180808050846.GG24415@xz-mi> (raw)
In-Reply-To: <20180807091209.13531-9-xiaoguangrong@tencent.com>

On Tue, Aug 07, 2018 at 05:12:07PM +0800, guangrong.xiao@gmail.com wrote:
> From: Xiao Guangrong <xiaoguangrong@tencent.com>
> 
> ram_find_and_save_block() can return negative if any error hanppens,
> however, it is completely ignored in current code

Could you hint me where we'll return an error?

(Anyway I agree that the error handling is not that good, mostly
 because the QEMUFile APIs does not provide proper return code, e.g.,
 qemu_put_be64 returns void)

> 
> Signed-off-by: Xiao Guangrong <xiaoguangrong@tencent.com>
> ---
>  migration/ram.c | 18 +++++++++++++++---
>  1 file changed, 15 insertions(+), 3 deletions(-)
> 
> diff --git a/migration/ram.c b/migration/ram.c
> index 55966bc2c1..09be01dca2 100644
> --- a/migration/ram.c
> +++ b/migration/ram.c
> @@ -2367,7 +2367,8 @@ static int ram_save_host_page(RAMState *rs, PageSearchStatus *pss,
>   *
>   * Called within an RCU critical section.
>   *
> - * Returns the number of pages written where zero means no dirty pages
> + * Returns the number of pages written where zero means no dirty pages,
> + * or negative on error
>   *
>   * @rs: current RAM state
>   * @last_stage: if we are at the completion stage
> @@ -3202,6 +3203,12 @@ static int ram_save_iterate(QEMUFile *f, void *opaque)
>              done = 1;
>              break;
>          }
> +
> +        if (pages < 0) {
> +            qemu_file_set_error(f, pages);
> +            break;
> +        }
> +
>          rs->iterations++;
>  
>          /* we want to check in the 1st loop, just in case it was the 1st time
> @@ -3243,7 +3250,7 @@ out:
>  /**
>   * ram_save_complete: function called to send the remaining amount of ram
>   *
> - * Returns zero to indicate success
> + * Returns zero to indicate success or negative on error
>   *
>   * Called with iothread lock
>   *
> @@ -3254,6 +3261,7 @@ static int ram_save_complete(QEMUFile *f, void *opaque)
>  {
>      RAMState **temp = opaque;
>      RAMState *rs = *temp;
> +    int ret = 0;
>  
>      rcu_read_lock();
>  
> @@ -3274,6 +3282,10 @@ static int ram_save_complete(QEMUFile *f, void *opaque)
>          if (pages == 0) {
>              break;
>          }
> +        if (pages < 0) {
> +            ret = pages;
> +            break;
> +        }
>      }
>  
>      flush_compressed_data(rs);
> @@ -3285,7 +3297,7 @@ static int ram_save_complete(QEMUFile *f, void *opaque)
>      qemu_put_be64(f, RAM_SAVE_FLAG_EOS);
>      qemu_fflush(f);
>  
> -    return 0;
> +    return ret;
>  }
>  
>  static void ram_save_pending(QEMUFile *f, void *opaque, uint64_t max_size,
> -- 
> 2.14.4
> 

Regards,

-- 
Peter Xu

WARNING: multiple messages have this Message-ID (diff)
From: Peter Xu <peterx@redhat.com>
To: guangrong.xiao@gmail.com
Cc: pbonzini@redhat.com, mst@redhat.com, mtosatti@redhat.com,
	qemu-devel@nongnu.org, kvm@vger.kernel.org, dgilbert@redhat.com,
	wei.w.wang@intel.com, jiang.biao2@zte.com.cn, eblake@redhat.com,
	Xiao Guangrong <xiaoguangrong@tencent.com>
Subject: Re: [Qemu-devel] [PATCH v3 08/10] migration: handle the error condition properly
Date: Wed, 8 Aug 2018 13:08:46 +0800	[thread overview]
Message-ID: <20180808050846.GG24415@xz-mi> (raw)
In-Reply-To: <20180807091209.13531-9-xiaoguangrong@tencent.com>

On Tue, Aug 07, 2018 at 05:12:07PM +0800, guangrong.xiao@gmail.com wrote:
> From: Xiao Guangrong <xiaoguangrong@tencent.com>
> 
> ram_find_and_save_block() can return negative if any error hanppens,
> however, it is completely ignored in current code

Could you hint me where we'll return an error?

(Anyway I agree that the error handling is not that good, mostly
 because the QEMUFile APIs does not provide proper return code, e.g.,
 qemu_put_be64 returns void)

> 
> Signed-off-by: Xiao Guangrong <xiaoguangrong@tencent.com>
> ---
>  migration/ram.c | 18 +++++++++++++++---
>  1 file changed, 15 insertions(+), 3 deletions(-)
> 
> diff --git a/migration/ram.c b/migration/ram.c
> index 55966bc2c1..09be01dca2 100644
> --- a/migration/ram.c
> +++ b/migration/ram.c
> @@ -2367,7 +2367,8 @@ static int ram_save_host_page(RAMState *rs, PageSearchStatus *pss,
>   *
>   * Called within an RCU critical section.
>   *
> - * Returns the number of pages written where zero means no dirty pages
> + * Returns the number of pages written where zero means no dirty pages,
> + * or negative on error
>   *
>   * @rs: current RAM state
>   * @last_stage: if we are at the completion stage
> @@ -3202,6 +3203,12 @@ static int ram_save_iterate(QEMUFile *f, void *opaque)
>              done = 1;
>              break;
>          }
> +
> +        if (pages < 0) {
> +            qemu_file_set_error(f, pages);
> +            break;
> +        }
> +
>          rs->iterations++;
>  
>          /* we want to check in the 1st loop, just in case it was the 1st time
> @@ -3243,7 +3250,7 @@ out:
>  /**
>   * ram_save_complete: function called to send the remaining amount of ram
>   *
> - * Returns zero to indicate success
> + * Returns zero to indicate success or negative on error
>   *
>   * Called with iothread lock
>   *
> @@ -3254,6 +3261,7 @@ static int ram_save_complete(QEMUFile *f, void *opaque)
>  {
>      RAMState **temp = opaque;
>      RAMState *rs = *temp;
> +    int ret = 0;
>  
>      rcu_read_lock();
>  
> @@ -3274,6 +3282,10 @@ static int ram_save_complete(QEMUFile *f, void *opaque)
>          if (pages == 0) {
>              break;
>          }
> +        if (pages < 0) {
> +            ret = pages;
> +            break;
> +        }
>      }
>  
>      flush_compressed_data(rs);
> @@ -3285,7 +3297,7 @@ static int ram_save_complete(QEMUFile *f, void *opaque)
>      qemu_put_be64(f, RAM_SAVE_FLAG_EOS);
>      qemu_fflush(f);
>  
> -    return 0;
> +    return ret;
>  }
>  
>  static void ram_save_pending(QEMUFile *f, void *opaque, uint64_t max_size,
> -- 
> 2.14.4
> 

Regards,

-- 
Peter Xu

  reply	other threads:[~2018-08-08  5:08 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-07  9:11 [PATCH v3 00/10] migration: compression optimization guangrong.xiao
2018-08-07  9:11 ` [Qemu-devel] " guangrong.xiao
2018-08-07  9:12 ` [PATCH v3 01/10] migration: do not wait for free thread guangrong.xiao
2018-08-07  9:12   ` [Qemu-devel] " guangrong.xiao
2018-08-07 13:29   ` Eric Blake
2018-08-07 13:29     ` [Qemu-devel] " Eric Blake
2018-08-08  3:51     ` Peter Xu
2018-08-08  3:51       ` [Qemu-devel] " Peter Xu
2018-08-08  6:20       ` Xiao Guangrong
2018-08-08  6:20         ` [Qemu-devel] " Xiao Guangrong
2018-08-07  9:12 ` [PATCH v3 02/10] migration: fix counting normal page for compression guangrong.xiao
2018-08-07  9:12   ` [Qemu-devel] " guangrong.xiao
2018-08-07  9:12 ` [PATCH v3 03/10] migration: introduce save_zero_page_to_file guangrong.xiao
2018-08-07  9:12   ` [Qemu-devel] " guangrong.xiao
2018-08-07  9:12 ` [PATCH v3 04/10] migration: drop the return value of do_compress_ram_page guangrong.xiao
2018-08-07  9:12   ` [Qemu-devel] " guangrong.xiao
2018-08-07  9:12 ` [PATCH v3 05/10] migration: move handle of zero page to the thread guangrong.xiao
2018-08-07  9:12   ` [Qemu-devel] " guangrong.xiao
2018-08-08  4:39   ` Peter Xu
2018-08-08  4:39     ` [Qemu-devel] " Peter Xu
2018-08-07  9:12 ` [PATCH v3 06/10] migration: hold the lock only if it is really needed guangrong.xiao
2018-08-07  9:12   ` [Qemu-devel] " guangrong.xiao
2018-08-07  9:12 ` [PATCH v3 07/10] migration: do not flush_compressed_data at the end of each iteration guangrong.xiao
2018-08-07  9:12   ` [Qemu-devel] " guangrong.xiao
2018-08-08  4:52   ` Peter Xu
2018-08-08  4:52     ` [Qemu-devel] " Peter Xu
2018-08-08  6:22     ` Xiao Guangrong
2018-08-08  6:22       ` [Qemu-devel] " Xiao Guangrong
2018-08-07  9:12 ` [PATCH v3 08/10] migration: handle the error condition properly guangrong.xiao
2018-08-07  9:12   ` [Qemu-devel] " guangrong.xiao
2018-08-08  5:08   ` Peter Xu [this message]
2018-08-08  5:08     ` Peter Xu
2018-08-08  6:29     ` Xiao Guangrong
2018-08-08  6:29       ` [Qemu-devel] " Xiao Guangrong
2018-08-08  6:56       ` Peter Xu
2018-08-08  6:56         ` [Qemu-devel] " Peter Xu
2018-08-08  7:23         ` Xiao Guangrong
2018-08-08  7:23           ` [Qemu-devel] " Xiao Guangrong
2018-08-08  8:46           ` Peter Xu
2018-08-08  8:46             ` [Qemu-devel] " Peter Xu
2018-08-08 14:11       ` Dr. David Alan Gilbert
2018-08-08 14:11         ` [Qemu-devel] " Dr. David Alan Gilbert
2018-08-09  3:08         ` Xiao Guangrong
2018-08-09  3:08           ` [Qemu-devel] " Xiao Guangrong
2018-08-07  9:12 ` [PATCH v3 09/10] migration: fix calculating xbzrle_counters.cache_miss_rate guangrong.xiao
2018-08-07  9:12   ` [Qemu-devel] " guangrong.xiao
2018-08-08  6:05   ` Peter Xu
2018-08-08  6:05     ` [Qemu-devel] " Peter Xu
2018-08-08  6:36     ` Xiao Guangrong
2018-08-08  6:36       ` [Qemu-devel] " Xiao Guangrong
2018-08-08  6:59       ` Peter Xu
2018-08-08  6:59         ` [Qemu-devel] " Peter Xu
2018-08-07  9:12 ` [PATCH v3 10/10] migration: show the statistics of compression guangrong.xiao
2018-08-07  9:12   ` [Qemu-devel] " guangrong.xiao
2018-08-08  6:12   ` Peter Xu
2018-08-08  6:12     ` [Qemu-devel] " Peter Xu
2018-08-09  3:13     ` Xiao Guangrong
2018-08-09  3:13       ` [Qemu-devel] " Xiao Guangrong
2018-08-09  3:34       ` Peter Xu
2018-08-09  3:34         ` [Qemu-devel] " Peter Xu

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=20180808050846.GG24415@xz-mi \
    --to=peterx@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=guangrong.xiao@gmail.com \
    --cc=jiang.biao2@zte.com.cn \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wei.w.wang@intel.com \
    --cc=xiaoguangrong@tencent.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.