linux-kernel - Re: [PATCH v4 00/12] KVM: x86/mmu: refine memtype related mmu zap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZPWZwJ8KQXbWwvxC@yzhao56-desk.sh.intel.com>
Date:   Mon, 4 Sep 2023 16:48:00 +0800
From:   Yan Zhao <yan.y.zhao@...el.com>
To:     Sean Christopherson <seanjc@...gle.com>
CC:     <kvm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <pbonzini@...hat.com>, <chao.gao@...el.com>, <kai.huang@...el.com>,
        <robert.hoo.linux@...il.com>, <yuan.yao@...ux.intel.com>
Subject: Re: [PATCH v4 00/12] KVM: x86/mmu: refine memtype related mmu zap

On Fri, Aug 25, 2023 at 04:17:09PM -0700, Sean Christopherson wrote:
> On Fri, Jul 14, 2023, Yan Zhao wrote:
> > This series refines mmu zap caused by EPT memory type update when guest
> > MTRRs are honored.
> > 
> > Patches 1-5 revolve around utilizing helper functions to check if
> > KVM TDP honors guest MTRRs, TDP zaps and page fault max_level reduction
> > are now only targeted to TDPs that honor guest MTRRs.
> > 
> > -The 5th patch will trigger zapping of TDP leaf entries if non-coherent
> >  DMA devices count goes from 0 to 1 or from 1 to 0.
> > 
> > Patches 6-7 are fixes and patches 9-12 are optimizations for mmu zaps
> > when guest MTRRs are honored.
> > Those mmu zaps are intended to remove stale memtypes of TDP entries
> > caused by changes of guest MTRRs and CR0.CD and are usually triggered from
> > all vCPUs in bursts.
> 
> Sorry for the delayed review, especially with respect to patches 1-5.  I completely
> forgot there were cleanups at the beginning of this series.  I'll make to grab
> 1-5 early in the 6.7 cycle, even if you haven't sent a new version before then.
Never mind and thanks a lot regarding to patches 1-5!
I may not be able to spin the next version soon as I got a high priority task and
I need to finish the task first (I wish I can complete it in 1-1.5 months)
Sorry and thanks again!