All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Xiao Guangrong <guangrong.xiao@gmail.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 v2 0/7] KVM: MMU: fast write protect
Date: Mon, 3 Jul 2017 17:47:30 +0200	[thread overview]
Message-ID: <6db0c80d-2ae2-9e89-356e-35acd241fdc5@redhat.com> (raw)
In-Reply-To: <4dffc169-5cf2-8f37-bd99-9941bef50825@gmail.com>



On 03/07/2017 16:39, Xiao Guangrong wrote:
> 
> 
> On 06/20/2017 05:15 PM, guangrong.xiao@gmail.com wrote:
>> From: Xiao Guangrong <xiaoguangrong@tencent.com>
>>
>> Changelog in v2:
>> thanks to Paolo's review, this version disables write-protect-all if
>> PML is supported
> 
> Hi Paolo,
> 
> Do you have time to have a look at this new version? ;)
> Or I should wait until the patchset of dirty ring-buffer is merged?

I will look at it soon, but I still plan to merge dirty ring buffer first.

Thanks for your understanding,

Paolo

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Xiao Guangrong <guangrong.xiao@gmail.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 v2 0/7] KVM: MMU: fast write protect
Date: Mon, 3 Jul 2017 17:47:30 +0200	[thread overview]
Message-ID: <6db0c80d-2ae2-9e89-356e-35acd241fdc5@redhat.com> (raw)
In-Reply-To: <4dffc169-5cf2-8f37-bd99-9941bef50825@gmail.com>



On 03/07/2017 16:39, Xiao Guangrong wrote:
> 
> 
> On 06/20/2017 05:15 PM, guangrong.xiao@gmail.com wrote:
>> From: Xiao Guangrong <xiaoguangrong@tencent.com>
>>
>> Changelog in v2:
>> thanks to Paolo's review, this version disables write-protect-all if
>> PML is supported
> 
> Hi Paolo,
> 
> Do you have time to have a look at this new version? ;)
> Or I should wait until the patchset of dirty ring-buffer is merged?

I will look at it soon, but I still plan to merge dirty ring buffer first.

Thanks for your understanding,

Paolo

  reply	other threads:[~2017-07-03 15:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20  9:15 [PATCH v2 0/7] KVM: MMU: fast write protect guangrong.xiao
2017-06-20  9:15 ` [Qemu-devel] " guangrong.xiao
2017-06-20  9:15 ` [PATCH v2 1/7] KVM: MMU: correct the behavior of mmu_spte_update_no_track guangrong.xiao
2017-06-20  9:15   ` [Qemu-devel] " guangrong.xiao
2017-06-20  9:15 ` [PATCH v2 2/7] KVM: MMU: introduce possible_writable_spte_bitmap guangrong.xiao
2017-06-20  9:15   ` [Qemu-devel] " guangrong.xiao
2017-06-20  9:15 ` [PATCH v2 3/7] KVM: MMU: introduce kvm_mmu_write_protect_all_pages guangrong.xiao
2017-06-20  9:15   ` [Qemu-devel] " guangrong.xiao
2017-06-20  9:15 ` [PATCH v2 4/7] KVM: MMU: enable KVM_WRITE_PROTECT_ALL_MEM guangrong.xiao
2017-06-20  9:15   ` [Qemu-devel] " guangrong.xiao
2017-06-20  9:15 ` [PATCH v2 5/7] KVM: MMU: allow dirty log without write protect guangrong.xiao
2017-06-20  9:15   ` [Qemu-devel] " guangrong.xiao
2017-06-20  9:15 ` [PATCH v2 6/7] KVM: MMU: clarify fast_pf_fix_direct_spte guangrong.xiao
2017-06-20  9:15   ` [Qemu-devel] " guangrong.xiao
2017-06-20  9:15 ` [PATCH v2 7/7] KVM: MMU: stop using mmu_spte_get_lockless under mmu-lock guangrong.xiao
2017-06-20  9:15   ` [Qemu-devel] " guangrong.xiao
2017-07-03 14:39 ` [PATCH v2 0/7] KVM: MMU: fast write protect Xiao Guangrong
2017-07-03 14:39   ` [Qemu-devel] " Xiao Guangrong
2017-07-03 15:47   ` Paolo Bonzini [this message]
2017-07-03 15:47     ` Paolo Bonzini
2017-07-04  3:17     ` Xiao Guangrong
2017-07-04  3:17       ` [Qemu-devel] " 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=6db0c80d-2ae2-9e89-356e-35acd241fdc5@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=avi.kivity@gmail.com \
    --cc=guangrong.xiao@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rkrcmar@redhat.com \
    --cc=xiaoguangrong@tencent.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 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.