[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZG1XOHBKZbxNEjQK@google.com>
Date: Tue, 23 May 2023 17:15:52 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Yan Zhao <yan.y.zhao@...el.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
pbonzini@...hat.com
Subject: Re: [PATCH v2 0/6] KVM: x86/mmu: refine memtype related mmu zap
On Tue, May 09, 2023, Yan Zhao wrote:
> This series refines mmu zap caused by EPT memory type update.
> Yan Zhao (6):
> KVM: x86/mmu: add a new mmu zap helper to indicate memtype changes
> KVM: x86/mmu: only zap EPT when guest CR0_CD changes
> KVM: x86/mmu: only zap EPT when guest MTRR changes
> KVM: x86/mmu: Zap all EPT leaf entries according noncoherent DMA count
> KVM: x86: Keep a per-VM MTRR state
> KVM: x86/mmu: use per-VM based MTRR for EPT
>
> arch/x86/include/asm/kvm_host.h | 3 +
> arch/x86/kvm/mmu.h | 1 +
> arch/x86/kvm/mmu/mmu.c | 18 ++++-
> arch/x86/kvm/mtrr.c | 112 +++++++++++++++++++++++++-------
> arch/x86/kvm/vmx/vmx.c | 2 +-
> arch/x86/kvm/x86.c | 10 ++-
> arch/x86/kvm/x86.h | 6 +-
> 7 files changed, 122 insertions(+), 30 deletions(-)
>
>
> base-commit: 5c291b93e5d665380dbecc6944973583f9565ee5
> --
To save us both a bit of pain, can you base the next version on top of my PAT
cleanup[*]? I am planning on applying that series "soon". Thanks!
[*] https://lore.kernel.org/all/20230511233351.635053-1-seanjc@google.com
Powered by blists - more mailing lists