From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Xu <peterx@redhat.com>,
QEMU Devel Mailing List <qemu-devel@nongnu.org>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: Question on dirty sync before kvm memslot removal
Date: Mon, 30 Mar 2020 15:11:53 +0200 [thread overview]
Message-ID: <c90a6ffd-0cab-186d-b9c8-8e379921783f@redhat.com> (raw)
In-Reply-To: <20200327150425.GJ422390@xz-x1>
On 27/03/20 16:04, Peter Xu wrote:
> That makes perfect sense to me, however... What if the vcpu generates
> dirty bits _after_ we do KVM_GET_DIRTY_LOG but _before_ we send
> KVM_SET_USER_MEMORY_REGION to remove the memslot? If the vcpu is in
> the userspace I think it's fine because BQL is needed so it won't be
> able to, however the vcpus running inside KVM should not be restricted
> to that. I think those dirty bits will still get lost, but it should
> be extremely hard to trigger.
Yes, you've found a bug.
> I'm not sure whether I missed something above, but if I'm correct, I
> think the solution should be a flag for KVM_SET_USER_MEMORY_REGION to
> set the memslot as invalid (KVM_MEM_INVALID), then when removing the
> memslot which has KVM_MEM_LOG_DIRTY_PAGES enabled, we should:
>
> - send KVM_SET_USER_MEMORY_REGION with KVM_MEM_INVALID to invalidate
> the memslot, but keep the slot and bitmap in KVM
>
> - send KVM_GET_DIRTY_LOG to fetch the bitmap for the slot
>
> - send KVM_SET_USER_MEMORY_REGION with size==0 to remove the slot
Or KVM_MEM_READONLY.
> However I don't know whether that'll worth it.
Yes, especially in the light of the dirty ring issue below.
> (Side question which is irrelevant to this: for kvm dirty ring we now
> need to do similar thing to flush dirty bits before removing a
> memslot, however that's even trickier because flushing dirty ring
> needs to kick all vcpu out, currently the RFC series is using
> run_on_cpu() which will release the BQL and wait for all vcpus to
> quit into userspace, however that cannot be done inside
> kvm_set_phys_mem because it needs the BQL. I'm still thinking about
> a good way to fix this, but any idea is greatly welcomed :)
The problem here is also that the GFN is not an unique identifier of the
QEMU ram_addr_t. However you don't really need to kick all vCPUs out,
do you? You can protect the dirty ring with its own per-vCPU mutex and
harvest the pages from the main thread.
Paolo
next prev parent reply other threads:[~2020-03-30 13:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 15:04 Question on dirty sync before kvm memslot removal Peter Xu
2020-03-30 13:11 ` Paolo Bonzini [this message]
2020-03-31 15:23 ` Peter Xu
2020-03-31 15:34 ` Paolo Bonzini
2020-03-31 16:51 ` Peter Xu
2020-03-31 23:12 ` Paolo Bonzini
2020-04-01 23:09 ` Peter Xu
2020-04-02 20:47 ` Peter Xu
2020-04-02 22:32 ` 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=c90a6ffd-0cab-186d-b9c8-8e379921783f@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgilbert@redhat.com \
--cc=peterx@redhat.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).