From: Paolo Bonzini <pbonzini@redhat.com>
To: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>, gleb@kernel.org
Cc: avi.kivity@gmail.com, mtosatti@redhat.com,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH v4 0/5] KVM: x86: flush tlb out of mmu-lock after write protection
Date: Tue, 25 Mar 2014 11:22:07 +0100 [thread overview]
Message-ID: <533158CF.9040303@redhat.com> (raw)
In-Reply-To: <5330F82D.4070601@linux.vnet.ibm.com>
Il 25/03/2014 04:29, Xiao Guangrong ha scritto:
> Ping......
Hi Xiao, I'll look at these patches soon. I plan to merge them for 3.16.
Paolo
> On 03/10/2014 10:01 PM, Xiao Guangrong wrote:
>> This patchset is splited from my previous patchset:
>> [PATCH v3 00/15] KVM: MMU: locklessly write-protect
>> that can be found at:
>> https://lkml.org/lkml/2013/10/23/265
>>
>> Changelog v4 :
>> - add more comments for patch 5 and thank for Marcelo's review
>>
>> Xiao Guangrong (5):
>> Revert "KVM: Simplify kvm->tlbs_dirty handling"
>> KVM: MMU: properly check last spte in fast_page_fault()
>> KVM: MMU: lazily drop large spte
>> KVM: MMU: flush tlb if the spte can be locklessly modified
>> KVM: MMU: flush tlb out of mmu lock when write-protect the sptes
>>
>> arch/x86/kvm/mmu.c | 72 ++++++++++++++++++++++++++++++----------------
>> arch/x86/kvm/mmu.h | 14 +++++++++
>> arch/x86/kvm/paging_tmpl.h | 7 ++---
>> arch/x86/kvm/x86.c | 20 ++++++++++---
>> include/linux/kvm_host.h | 4 +--
>> virt/kvm/kvm_main.c | 5 +++-
>> 6 files changed, 85 insertions(+), 37 deletions(-)
>>
>
next prev parent reply other threads:[~2014-03-25 10:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 14:01 [PATCH v4 0/5] KVM: x86: flush tlb out of mmu-lock after write protection Xiao Guangrong
2014-03-10 14:01 ` [PATCH 1/5] Revert "KVM: Simplify kvm->tlbs_dirty handling" Xiao Guangrong
2014-03-10 14:01 ` [PATCH 2/5] KVM: MMU: properly check last spte in fast_page_fault() Xiao Guangrong
2014-03-10 14:01 ` [PATCH 3/5] KVM: MMU: lazily drop large spte Xiao Guangrong
2014-03-10 14:01 ` [PATCH 4/5] KVM: MMU: flush tlb if the spte can be locklessly modified Xiao Guangrong
2014-03-10 14:01 ` [PATCH 5/5] KVM: MMU: flush tlb out of mmu lock when write-protect the sptes Xiao Guangrong
2014-04-09 14:51 ` Marcelo Tosatti
2014-04-15 11:11 ` Xiao Guangrong
2014-03-25 3:29 ` [PATCH v4 0/5] KVM: x86: flush tlb out of mmu-lock after write protection Xiao Guangrong
2014-03-25 10:22 ` Paolo Bonzini [this message]
2014-03-25 16:25 ` Hu Yaohui
2014-03-26 4:40 ` Hu Yaohui
2014-03-26 5:07 ` Xiao Guangrong
2014-03-26 5:30 ` Hu Yaohui
2014-03-26 4:54 ` 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=533158CF.9040303@redhat.com \
--to=pbonzini@redhat.com \
--cc=avi.kivity@gmail.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=xiaoguangrong@linux.vnet.ibm.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.