From: Eric Blake <eblake@redhat.com>
To: Vincent KHERBACHE <vincent.kherbache@inria.fr>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, gleb@redhat.com
Subject: Re: [Qemu-devel] [PATCH] kvm: fix kvm_set_migration_log() behavior
Date: Tue, 18 Feb 2014 06:23:04 -0700 [thread overview]
Message-ID: <53035EB8.4050206@redhat.com> (raw)
In-Reply-To: <1392726818-14606-1-git-send-email-vincent.kherbache@inria.fr>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
On 02/18/2014 05:33 AM, Vincent KHERBACHE wrote:
> The test (!!(mem->flags & KVM_MEM_LOG_DIRTY_PAGES) == enable) is wrong because
> the condition is valid when enable = 0 and current dirty log memory flag is set.
> As a consequence kvm_log_global_stop() does not stop the KVM dirty log
> tracking: kvm_set_migration_log(0) didn't do its job.
> So instead I propose to use kvm_slot_dirty_pages_log_change() which correctly
> compare the memory flags (old/new).
>
> Signed-off-by: Vincent KHERBACHE <vincent.kherbache@inria.fr>
> ---
> kvm-all.c | 12 +++---------
> 1 file changed, 3 insertions(+), 9 deletions(-)
>
> - return err;
> - }
> + err = kvm_slot_dirty_pages_log_change(mem, (bool)enable);
Is this a v2 post? Any reason you reposted without addressing my
earlier review?
https://lists.gnu.org/archive/html/qemu-devel/2014-02/msg02840.html
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-02-18 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 12:33 [Qemu-devel] [PATCH] kvm: fix kvm_set_migration_log() behavior Vincent KHERBACHE
2014-02-18 13:23 ` Eric Blake [this message]
2014-02-18 14:34 ` Vincent KHERBACHE
2014-02-18 16:16 ` Paolo Bonzini
2014-02-18 17:58 ` Vincent KHERBACHE
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=53035EB8.4050206@redhat.com \
--to=eblake@redhat.com \
--cc=gleb@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vincent.kherbache@inria.fr \
/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.