From: Paolo Bonzini <pbonzini@redhat.com>
To: lantianyu1986@gmail.com
Cc: Lan Tianyu <Tianyu.Lan@microsoft.com>,
benh@kernel.crashing.org, bp@alien8.de, catalin.marinas@arm.com,
christoffer.dall@arm.com, devel@linuxdriverproject.org,
haiyangz@microsoft.com, hpa@zytor.com, jhogan@kernel.org,
kvmarm@lists.cs.columbia.edu, kvm-ppc@vger.kernel.org,
kvm@vger.kernel.org, kys@microsoft.com,
linux-arm-kernel@lists.infradead.org, linux@armlinux.org.uk,
linux-kernel@vger.kernel.org, linux-mips@linux-mips.org,
linuxppc-dev@lists.ozlabs.org, marc.zyngier@arm.com,
mingo@redhat.com, mpe@ellerman.id.au, paul.burton@mips.com,
paulus@ozlabs.org, ralf@linux-mips.org, rkrcmar@redhat.com,
sthemmin@microsoft.com, tglx@linutronix.de, will.deacon@arm.com,
x86@kernel.org, michael.h.kelley@microsoft.com,
vkuznets@redhat.com
Subject: Re: [Resend PATCH V5 0/10] x86/KVM/Hyper-v: Add HV ept tlb range flush hypercall support in KVM
Date: Fri, 21 Dec 2018 10:31:28 +0100 [thread overview]
Message-ID: <36f1e16f-2390-fa61-e5e0-07320abea9ba@redhat.com> (raw)
In-Reply-To: <20181206132113.2691-1-Tianyu.Lan@microsoft.com>
On 06/12/18 14:21, lantianyu1986@gmail.com wrote:
> From: Lan Tianyu <Tianyu.Lan@microsoft.com>
>
> For nested memory virtualization, Hyper-v doesn't set write-protect
> L1 hypervisor EPT page directory and page table node to track changes
> while it relies on guest to tell it changes via HvFlushGuestAddressLlist
> hypercall. HvFlushGuestAddressLlist hypercall provides a way to flush
> EPT page table with ranges which are specified by L1 hypervisor.
>
> If L1 hypervisor uses INVEPT or HvFlushGuestAddressSpace hypercall to
> flush EPT tlb, Hyper-V will invalidate associated EPT shadow page table
> and sync L1's EPT table when next EPT page fault is triggered.
> HvFlushGuestAddressLlist hypercall helps to avoid such redundant EPT
> page fault and synchronization of shadow page table.
>
> This patchset is based on the Patch "KVM/VMX: Check ept_pointer before
> flushing ept tlb"(https://marc.info/?l=kvm&m=154408169705686&w=2).
>
> Change since v4:
> 1) Split flush address and flush list patches. This patchset only contains
> flush address patches. Will post flush list patches later.
> 2) Expose function hyperv_fill_flush_guest_mapping_list()
> out of hyperv file
> 3) Adjust parameter of hyperv_flush_guest_mapping_range()
> 4) Reorder patchset and move Hyper-V and VMX changes ahead.
>
> Change since v3:
> 1) Remove code of updating "tlbs_dirty" in kvm_flush_remote_tlbs_with_range()
> 2) Remove directly tlb flush in the kvm_handle_hva_range()
> 3) Move tlb flush in kvm_set_pte_rmapp() to kvm_mmu_notifier_change_pte()
> 4) Combine Vitaly's "don't pass EPT configuration info to
> vmx_hv_remote_flush_tlb()" fix
>
> Change since v2:
> 1) Fix comment in the kvm_flush_remote_tlbs_with_range()
> 2) Move HV_MAX_FLUSH_PAGES and HV_MAX_FLUSH_REP_COUNT to
> hyperv-tlfs.h.
> 3) Calculate HV_MAX_FLUSH_REP_COUNT in the macro definition
> 4) Use HV_MAX_FLUSH_REP_COUNT to define length of gpa_list in
> struct hv_guest_mapping_flush_list.
>
> Change since v1:
> 1) Convert "end_gfn" of struct kvm_tlb_range to "pages" in order
> to avoid confusion as to whether "end_gfn" is inclusive or exlusive.
> 2) Add hyperv tlb range struct and replace kvm tlb range struct
> with new struct in order to avoid using kvm struct in the hyperv
> code directly.
>
>
>
> Lan Tianyu (10):
> KVM: Add tlb_remote_flush_with_range callback in kvm_x86_ops
> x86/hyper-v: Add HvFlushGuestAddressList hypercall support
> x86/Hyper-v: Add trace in the
> hyperv_nested_flush_guest_mapping_range()
> KVM/VMX: Add hv tlb range flush support
> KVM/MMU: Add tlb flush with range helper function
> KVM: Replace old tlb flush function with new one to flush a specified
> range.
> KVM: Make kvm_set_spte_hva() return int
> KVM/MMU: Move tlb flush in kvm_set_pte_rmapp() to
> kvm_mmu_notifier_change_pte()
> KVM/MMU: Flush tlb directly in the kvm_set_pte_rmapp()
> KVM/MMU: Flush tlb directly in the kvm_zap_gfn_range()
>
> arch/arm/include/asm/kvm_host.h | 2 +-
> arch/arm64/include/asm/kvm_host.h | 2 +-
> arch/mips/include/asm/kvm_host.h | 2 +-
> arch/mips/kvm/mmu.c | 3 +-
> arch/powerpc/include/asm/kvm_host.h | 2 +-
> arch/powerpc/kvm/book3s.c | 3 +-
> arch/powerpc/kvm/e500_mmu_host.c | 3 +-
> arch/x86/hyperv/nested.c | 80 +++++++++++++++++++++++++++++++
> arch/x86/include/asm/hyperv-tlfs.h | 32 +++++++++++++
> arch/x86/include/asm/kvm_host.h | 9 +++-
> arch/x86/include/asm/mshyperv.h | 15 ++++++
> arch/x86/include/asm/trace/hyperv.h | 14 ++++++
> arch/x86/kvm/mmu.c | 96 +++++++++++++++++++++++++++++--------
> arch/x86/kvm/paging_tmpl.h | 3 +-
> arch/x86/kvm/vmx.c | 63 +++++++++++++++++-------
> virt/kvm/arm/mmu.c | 6 ++-
> virt/kvm/kvm_main.c | 5 +-
> 17 files changed, 292 insertions(+), 48 deletions(-)
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2018-12-21 9:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 13:21 [Resend PATCH V5 0/10] x86/KVM/Hyper-v: Add HV ept tlb range flush hypercall support in KVM lantianyu1986
2018-12-06 13:21 ` [Resend PATCH V5 1/10] KVM: Add tlb_remote_flush_with_range callback in kvm_x86_ops lantianyu1986
2018-12-06 13:21 ` [Resend PATCH V5 2/10] x86/hyper-v: Add HvFlushGuestAddressList hypercall support lantianyu1986
2018-12-21 9:32 ` Paolo Bonzini
2018-12-06 13:21 ` [Resend PATCH V5 3/10] x86/Hyper-v: Add trace in the hyperv_nested_flush_guest_mapping_range() lantianyu1986
2018-12-06 13:21 ` [Resend PATCH V5 4/10] KVM/VMX: Add hv tlb range flush support lantianyu1986
2018-12-06 13:21 ` [Resend PATCH V5 5/10] KVM/MMU: Add tlb flush with range helper function lantianyu1986
2018-12-06 13:21 ` [Resend PATCH V5 6/10] KVM: Replace old tlb flush function with new one to flush a specified range lantianyu1986
2018-12-06 13:21 ` [Resend PATCH V5 7/10] KVM: Make kvm_set_spte_hva() return int lantianyu1986
2018-12-12 5:03 ` Paul Mackerras
2018-12-13 7:47 ` Tianyu Lan
2018-12-06 13:21 ` [Resend PATCH V5 8/10] KVM/MMU: Move tlb flush in kvm_set_pte_rmapp() to kvm_mmu_notifier_change_pte() lantianyu1986
2018-12-06 13:21 ` [Resend PATCH V5 9/10] KVM/MMU: Flush tlb directly in the kvm_set_pte_rmapp() lantianyu1986
2018-12-06 13:21 ` [Resend PATCH V5 10/10] KVM/MMU: Flush tlb directly in the kvm_zap_gfn_range() lantianyu1986
2018-12-21 9:31 ` Paolo Bonzini [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=36f1e16f-2390-fa61-e5e0-07320abea9ba@redhat.com \
--to=pbonzini@redhat.com \
--cc=Tianyu.Lan@microsoft.com \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@arm.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=jhogan@kernel.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kys@microsoft.com \
--cc=lantianyu1986@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=marc.zyngier@arm.com \
--cc=michael.h.kelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paul.burton@mips.com \
--cc=paulus@ozlabs.org \
--cc=ralf@linux-mips.org \
--cc=rkrcmar@redhat.com \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
/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).