From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Christophe de Dinechin <dinechin@redhat.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Lei Cao <lei.cao@stratus.com>
Subject: Re: [PATCH RESEND v2 08/17] KVM: X86: Implement ring-based dirty memory tracking
Date: Wed, 8 Jan 2020 20:44:32 +0100 [thread overview]
Message-ID: <03e0cc7c-f47b-bdfa-8266-c77dc0627096@redhat.com> (raw)
In-Reply-To: <20200108190639.GE7096@xz-x1>
On 08/01/20 20:06, Peter Xu wrote:
>> The kvmgt patches were posted, you could just include them in your next
>> series and clean everything up. You can get them at
>> https://patchwork.kernel.org/cover/11316219/.
> Good to know!
>
> Maybe I'll simply drop all the redundants in the dirty ring series
> assuming it's there? Since these patchsets should not overlap with
> each other (so looks more like an ordering constraints for merging).
Just include the patches, we'll make sure to get an ACK from Alex.
Paolo
next prev parent reply other threads:[~2020-01-08 19:44 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-21 1:49 [PATCH RESEND v2 00/17] KVM: Dirty ring interface Peter Xu
2019-12-21 1:49 ` [PATCH RESEND v2 01/17] KVM: Remove kvm_read_guest_atomic() Peter Xu
2020-01-08 17:45 ` Paolo Bonzini
2019-12-21 1:49 ` [PATCH RESEND v2 02/17] KVM: X86: Change parameter for fast_page_fault tracepoint Peter Xu
2020-01-08 17:46 ` Paolo Bonzini
2019-12-21 1:49 ` [PATCH RESEND v2 03/17] KVM: X86: Don't track dirty for KVM_SET_[TSS_ADDR|IDENTITY_MAP_ADDR] Peter Xu
2019-12-21 13:51 ` Paolo Bonzini
2019-12-23 17:27 ` Peter Xu
2019-12-23 17:59 ` Paolo Bonzini
2019-12-23 20:10 ` Peter Xu
2020-01-08 17:46 ` Paolo Bonzini
2020-01-08 19:15 ` Peter Xu
2020-01-08 19:44 ` Paolo Bonzini
2020-01-08 21:02 ` Peter Xu
2019-12-21 1:49 ` [PATCH RESEND v2 04/17] KVM: Cache as_id in kvm_memory_slot Peter Xu
2020-01-08 17:47 ` Paolo Bonzini
2019-12-21 1:49 ` [PATCH RESEND v2 05/17] KVM: Add build-time error check on kvm_run size Peter Xu
2019-12-21 1:49 ` [PATCH RESEND v2 06/17] KVM: Pass in kvm pointer into mark_page_dirty_in_slot() Peter Xu
2020-01-08 17:47 ` Paolo Bonzini
2019-12-21 1:49 ` [PATCH RESEND v2 07/17] KVM: Move running VCPU from ARM to common code Peter Xu
2020-01-08 17:47 ` Paolo Bonzini
2019-12-21 1:49 ` [PATCH RESEND v2 08/17] KVM: X86: Implement ring-based dirty memory tracking Peter Xu
2019-12-24 6:16 ` Jason Wang
2019-12-24 15:08 ` Peter Xu
2019-12-25 3:23 ` Jason Wang
2020-01-08 15:52 ` Peter Xu
2020-01-08 17:41 ` Paolo Bonzini
2020-01-08 19:06 ` Peter Xu
2020-01-08 19:44 ` Paolo Bonzini [this message]
2020-01-08 19:59 ` Peter Xu
2020-01-08 20:06 ` Paolo Bonzini
2019-12-21 1:49 ` [PATCH RESEND v2 09/17] KVM: Make dirty ring exclusive to dirty bitmap log Peter Xu
2019-12-21 1:58 ` [PATCH RESEND v2 10/17] KVM: Don't allocate dirty bitmap if dirty ring is enabled Peter Xu
2019-12-21 2:04 ` [PATCH RESEND v2 11/17] KVM: selftests: Always clear dirty bitmap after iteration Peter Xu
2019-12-21 2:04 ` [PATCH RESEND v2 12/17] KVM: selftests: Sync uapi/linux/kvm.h to tools/ Peter Xu
2019-12-21 2:04 ` [PATCH RESEND v2 13/17] KVM: selftests: Use a single binary for dirty/clear log test Peter Xu
2019-12-21 2:04 ` [PATCH RESEND v2 14/17] KVM: selftests: Introduce after_vcpu_run hook for dirty " Peter Xu
2019-12-21 2:04 ` [PATCH RESEND v2 15/17] KVM: selftests: Add dirty ring buffer test Peter Xu
2019-12-24 6:18 ` Jason Wang
2019-12-24 15:22 ` Peter Xu
2019-12-24 6:50 ` Jason Wang
2019-12-24 15:24 ` Peter Xu
2019-12-21 2:04 ` [PATCH RESEND v2 16/17] KVM: selftests: Let dirty_log_test async for dirty ring test Peter Xu
2019-12-21 2:04 ` [PATCH RESEND v2 17/17] KVM: selftests: Add "-c" parameter to dirty log test Peter Xu
2019-12-24 6:34 ` [PATCH RESEND v2 00/17] KVM: Dirty ring interface Jason Wang
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=03e0cc7c-f47b-bdfa-8266-c77dc0627096@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgilbert@redhat.com \
--cc=dinechin@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lei.cao@stratus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=vkuznets@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
all inboxes | Powered by JetHome®