From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Keqian Zhu <zhukeqian1@huawei.com>,
Hyman <huangy81@chinatelecom.cn>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH v6 00/10] KVM: Dirty ring support (QEMU part)
Date: Thu, 29 Apr 2021 17:07:48 -0400 [thread overview]
Message-ID: <20210429210748.GG8339@xz-x1> (raw)
In-Reply-To: <20210324183954.345629-1-peterx@redhat.com>
On Wed, Mar 24, 2021 at 02:39:44PM -0400, Peter Xu wrote:
> This is v6 of the qemu dirty ring interface support.
>
> v6:
> - Fix slots_lock init [Keqian, Paolo]
> - Comment above KVM_CAP_MANUAL_DIRTY_LOG_PROTECT2 on todo (to enable
> KVM_CLEAR_DIRTY_LOG for dirty ring too) [Keqian, Paolo]
> - Fix comment for CPUState [Keqian]
Ping after v6.0 released (seems still ok to apply).
--
Peter Xu
prev parent reply other threads:[~2021-04-29 21:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 18:39 [PATCH v6 00/10] KVM: Dirty ring support (QEMU part) Peter Xu
2021-03-24 18:39 ` [PATCH v6 01/10] memory: Introduce log_sync_global() to memory listener Peter Xu
2021-03-24 18:39 ` [PATCH v6 02/10] KVM: Use a big lock to replace per-kml slots_lock Peter Xu
2021-03-24 18:39 ` [PATCH v6 03/10] KVM: Create the KVMSlot dirty bitmap on flag changes Peter Xu
2021-03-24 18:39 ` [PATCH v6 04/10] KVM: Provide helper to get kvm dirty log Peter Xu
2021-03-24 18:39 ` [PATCH v6 05/10] KVM: Provide helper to sync dirty bitmap from slot to ramblock Peter Xu
2021-03-24 18:39 ` [PATCH v6 06/10] KVM: Simplify dirty log sync in kvm_set_phys_mem Peter Xu
2021-03-24 18:39 ` [PATCH v6 07/10] KVM: Cache kvm slot dirty bitmap size Peter Xu
2021-03-24 18:39 ` [PATCH v6 08/10] KVM: Add dirty-gfn-count property Peter Xu
2021-03-24 18:39 ` [PATCH v6 09/10] KVM: Disable manual dirty log when dirty ring enabled Peter Xu
2021-03-24 18:41 ` [PATCH v6 10/10] KVM: Dirty ring support Peter Xu
2021-04-29 21:07 ` 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=20210429210748.GG8339@xz-x1 \
--to=peterx@redhat.com \
--cc=dgilbert@redhat.com \
--cc=huangy81@chinatelecom.cn \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhukeqian1@huawei.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;
as well as URLs for NNTP newsgroup(s).