[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CADrL8HUB9Nhtqu+b1HhfG33Wt6wkp3LYkxSa7Nv1GbX5+Vj=vQ@mail.gmail.com>
Date: Mon, 28 Jul 2025 17:19:18 -0700
From: James Houghton <jthoughton@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Paolo Bonzini <pbonzini@...hat.com>, Vipin Sharma <vipinsh@...gle.com>,
David Matlack <dmatlack@...gle.com>, kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 0/7] KVM: x86/mmu: Run TDP MMU NX huge page recovery
under MMU read lock
On Wed, Jul 23, 2025 at 1:44 PM Sean Christopherson <seanjc@...gle.com> wrote:
>
> On Mon, Jul 07, 2025, James Houghton wrote:
> > David Matlack (1):
> > KVM: selftests: Introduce a selftest to measure execution performance
> >
> > James Houghton (3):
> > KVM: x86/mmu: Only grab RCU lock for nx hugepage recovery for TDP MMU
> > KVM: selftests: Provide extra mmap flags in vm_mem_add()
> > KVM: selftests: Add an NX huge pages jitter test
> >
> > Vipin Sharma (3):
> > KVM: x86/mmu: Track TDP MMU NX huge pages separately
> > KVM: x86/mmu: Rename kvm_tdp_mmu_zap_sp() to better indicate its
> > purpose
> > KVM: x86/mmu: Recover TDP MMU NX huge pages using MMU read lock
>
> The KVM changes look good, no need for a v5 on that front (I'll do minor fixup
> when applying, which will be a few weeks from now, after 6.17-rc1) . Still
> working through the selftests.
Thanks!
Powered by blists - more mailing lists