From: Xiao Guangrong <guangrong.xiao@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
mtosatti@redhat.com, avi.kivity@gmail.com, rkrcmar@redhat.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
qemu-devel@nongnu.org, Xiao Guangrong <xiaoguangrong@tencent.com>
Subject: Re: [PATCH 0/7] KVM: MMU: fast write protect
Date: Tue, 23 May 2017 10:23:42 +0800 [thread overview]
Message-ID: <66307755-c542-32fe-f88d-82cd4402353b@gmail.com> (raw)
In-Reply-To: <71ca0408-4ec3-938c-2899-a4aa02ed3ab5@redhat.com>
Ping...
Sorry to disturb, just make this patchset not be missed. :)
On 05/04/2017 03:06 PM, Paolo Bonzini wrote:
>
>
> On 04/05/2017 05:36, Xiao Guangrong wrote:
>> Great.
>>
>> As there is no conflict between these two patchsets except dirty
>> ring pages takes benefit from write-protect-all, i think they
>> can be developed and iterated independently, right?
>
> I can certainly start reviewing this one.
>
> Paolo
>
>> Or you prefer to merge dirty ring pages first then review the
>> new version of this patchset later?
WARNING: multiple messages have this Message-ID
From: Xiao Guangrong <guangrong.xiao@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
mtosatti@redhat.com, avi.kivity@gmail.com, rkrcmar@redhat.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
qemu-devel@nongnu.org, Xiao Guangrong <xiaoguangrong@tencent.com>
Subject: Re: [Qemu-devel] [PATCH 0/7] KVM: MMU: fast write protect
Date: Tue, 23 May 2017 10:23:42 +0800 [thread overview]
Message-ID: <66307755-c542-32fe-f88d-82cd4402353b@gmail.com> (raw)
In-Reply-To: <71ca0408-4ec3-938c-2899-a4aa02ed3ab5@redhat.com>
Ping...
Sorry to disturb, just make this patchset not be missed. :)
On 05/04/2017 03:06 PM, Paolo Bonzini wrote:
>
>
> On 04/05/2017 05:36, Xiao Guangrong wrote:
>> Great.
>>
>> As there is no conflict between these two patchsets except dirty
>> ring pages takes benefit from write-protect-all, i think they
>> can be developed and iterated independently, right?
>
> I can certainly start reviewing this one.
>
> Paolo
>
>> Or you prefer to merge dirty ring pages first then review the
>> new version of this patchset later?
next prev parent reply other threads:[~2017-05-23 2:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 10:52 guangrong.xiao
2017-05-03 10:52 ` [Qemu-devel] " guangrong.xiao
2017-05-03 10:52 ` [PATCH 1/7] KVM: MMU: correct the behavior of mmu_spte_update_no_track guangrong.xiao
2017-05-03 10:52 ` [Qemu-devel] " guangrong.xiao
2017-05-03 10:52 ` [PATCH 2/7] KVM: MMU: introduce possible_writable_spte_bitmap guangrong.xiao
2017-05-03 10:52 ` [Qemu-devel] " guangrong.xiao
2017-05-03 10:52 ` [PATCH 3/7] KVM: MMU: introduce kvm_mmu_write_protect_all_pages guangrong.xiao
2017-05-03 10:52 ` [Qemu-devel] " guangrong.xiao
2017-05-03 10:52 ` [PATCH 4/7] KVM: MMU: enable KVM_WRITE_PROTECT_ALL_MEM guangrong.xiao
2017-05-03 10:52 ` [Qemu-devel] " guangrong.xiao
2017-05-03 10:52 ` [PATCH 5/7] KVM: MMU: allow dirty log without write protect guangrong.xiao
2017-05-03 10:52 ` [Qemu-devel] " guangrong.xiao
2017-05-03 10:52 ` [PATCH 6/7] KVM: MMU: clarify fast_pf_fix_direct_spte guangrong.xiao
2017-05-03 10:52 ` [Qemu-devel] " guangrong.xiao
2017-05-03 10:52 ` [PATCH 7/7] KVM: MMU: stop using mmu_spte_get_lockless under mmu-lock guangrong.xiao
2017-05-03 10:52 ` [Qemu-devel] " guangrong.xiao
2017-05-03 12:28 ` [PATCH 0/7] KVM: MMU: fast write protect Paolo Bonzini
2017-05-03 12:28 ` [Qemu-devel] " Paolo Bonzini
2017-05-03 14:50 ` Xiao Guangrong
2017-05-03 14:50 ` [Qemu-devel] " Xiao Guangrong
2017-05-03 14:57 ` Paolo Bonzini
2017-05-03 14:57 ` [Qemu-devel] " Paolo Bonzini
2017-05-04 3:36 ` Xiao Guangrong
2017-05-04 3:36 ` [Qemu-devel] " Xiao Guangrong
2017-05-04 7:06 ` Paolo Bonzini
2017-05-04 7:06 ` [Qemu-devel] " Paolo Bonzini
2017-05-23 2:23 ` Xiao Guangrong [this message]
2017-05-23 2:23 ` Xiao Guangrong
2017-05-29 16:48 ` Paolo Bonzini
2017-05-29 16:48 ` [Qemu-devel] " Paolo Bonzini
2017-06-09 3:19 ` Xiao Guangrong
2017-06-09 3:19 ` [Qemu-devel] " Xiao Guangrong
2017-06-05 7:36 ` Jay Zhou
2017-06-05 7:36 ` Jay Zhou
2017-06-06 2:56 ` Xiao Guangrong
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=66307755-c542-32fe-f88d-82cd4402353b@gmail.com \
--to=guangrong.xiao@gmail.com \
--cc=avi.kivity@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=xiaoguangrong@tencent.com \
--subject='Re: [PATCH 0/7] KVM: MMU: fast write protect' \
/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
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.