All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Yaniv Kamay <ykamay@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] qemu: fix physical memory migration
Date: Wed, 25 Mar 2009 14:05:41 +0200	[thread overview]
Message-ID: <49CA1E15.8040402@redhat.com> (raw)
In-Reply-To: <49C947B4.5030503@redhat.com>

Yaniv Kamay wrote:
> Hi,
>
> Attaching patch that:
>
>    1. Fix physical memory live migration.
>        - Stop dirty memory tracking after completion of memory transfer.
>        - In stage 3, updating  dirty memory bits before collecting  
> remaining dirty blocks
>             in order to prevent missing dirty blokes in the range of 
> current_addr to phys_ram_size while
>             no dirty blocks exist in the range 0 - (current_addr - 1)
>        2. Improve migration error handling

Please split into three separate patches.

>
> +void qemu_file_set_has_error(QEMUFile *f);

Better named qemu_file_set_error()?

> diff --git a/qemu/vl.c b/qemu/vl.c
> index 7ae266e..405212f 100644
> --- a/qemu/vl.c
> +++ b/qemu/vl.c
> @@ -3221,8 +3221,14 @@ static int ram_save_block(QEMUFile *f)
>      int found = 0;
>  
>      while (addr < phys_ram_size) {
> -        if (kvm_enabled() && current_addr == 0)
> -            kvm_update_dirty_pages_log(); /* FIXME: propagate errors */
> +        if (kvm_enabled() && current_addr == 0) {
> +            int r;
> +            if ((r = kvm_update_dirty_pages_log())) {

Compare against negative; it could return positive numbers in the future 
even on no error.

> +                printf("%s: update dirty pages log failed %d\n", 
> __FUNCTION__, r);

qemu_log (in qemu-log.h)


-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2009-03-25 12:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 20:51 [PATCH] qemu: fix physical memory migration Yaniv Kamay
2009-03-25 12:05 ` Avi Kivity [this message]

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=49CA1E15.8040402@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=ykamay@redhat.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.