From: Peter Xu <peterx@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, "Juan Quintela" <quintela@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH 0/2] kvm: Some more trivial fixes for clear dirty log
Date: Wed, 8 May 2019 16:36:31 +0800 [thread overview]
Message-ID: <20190508083631.GA18465@xz-x1> (raw)
In-Reply-To: <a440e3f0-384b-2173-2c55-6cb2641f7937@redhat.com>
On Wed, May 08, 2019 at 10:12:49AM +0200, Paolo Bonzini wrote:
> On 08/05/19 00:44, Peter Xu wrote:
> > Two issues I've noticed when I'm drafting the QEMU support of it.
> > With these two patches applied the QEMU binary (with the clear dirty
> > log supported [1]) can migrate correctly otherwise the migration can
> > stall forever if with/after heavy memory workload.
> >
> > Please have a look, thanks.
> >
> > [1] https://github.com/xzpeter/qemu/tree/kvm-clear-dirty-log
> >
> > Peter Xu (2):
> > kvm: Fix the bitmap range to copy during clear dirty
> > kvm: Fix loop of clear dirty with off-by-one
> >
> > virt/kvm/kvm_main.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
>
> Looks good, but this is a blocker for using this feature in userspace.
> I think we should change the capability name and number.
Ok, let me add another patch for it. Also I probably have made a
mistake too in patch 2 (it's not really off-by-one, but it should be a
DIV_ROUND_UP I think...). I'll post a new version soon.
Thanks,
--
Peter Xu
prev parent reply other threads:[~2019-05-08 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 5:44 [PATCH 0/2] kvm: Some more trivial fixes for clear dirty log Peter Xu
2019-05-08 5:44 ` [PATCH 1/2] kvm: Fix the bitmap range to copy during clear dirty Peter Xu
2019-05-08 5:44 ` [PATCH 2/2] kvm: Fix loop of clear dirty with off-by-one Peter Xu
2019-05-08 8:12 ` [PATCH 0/2] kvm: Some more trivial fixes for clear dirty log Paolo Bonzini
2019-05-08 8:36 ` Peter Xu [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=20190508083631.GA18465@xz-x1 \
--to=peterx@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=quintela@redhat.com \
--cc=rkrcmar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox