linux-kernel - Re: [PATCH v3 00/16] Add Nested NPT support in selftests

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] [day] [month] [year] [list]

Message-ID: <bqq5iht35entb5oayouofi4o3v3adfjyi62dsjl6k7wdwkaaw4@ui4v7hymrn7w>
Date: Tue, 23 Dec 2025 23:48:32 +0000
From: Yosry Ahmed <yosry.ahmed@...ux.dev>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Paolo Bonzini <pbonzini@...hat.com>, kvm@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 00/16] Add Nested NPT support in selftests

On Tue, Dec 23, 2025 at 02:01:36PM -0800, Sean Christopherson wrote:
> On Thu, Nov 27, 2025, Yosry Ahmed wrote:
> > Yosry Ahmed (16):
> >   KVM: selftests: Make __vm_get_page_table_entry() static
> >   KVM: selftests: Stop passing a memslot to nested_map_memslot()
> >   KVM: selftests: Rename nested TDP mapping functions
> >   KVM: selftests: Kill eptPageTablePointer
> >   KVM: selftests: Stop setting AD bits on nested EPTs on creation
> >   KVM: selftests: Introduce struct kvm_mmu
> >   KVM: selftests: Move PTE bitmasks to kvm_mmu
> >   KVM: selftests: Use a nested MMU to share nested EPTs between vCPUs
> >   KVM: selftests: Stop passing VMX metadata to TDP mapping functions
> >   KVM: selftests: Reuse virt mapping functions for nested EPTs
> >   KVM: selftests: Move TDP mapping functions outside of vmx.c
> >   KVM: selftests: Allow kvm_cpu_has_ept() to be called on AMD CPUs
> >   KVM: selftests: Add support for nested NPTs
> >   KVM: selftests: Set the user bit on nested NPT PTEs
> >   KVM: selftests: Extend vmx_dirty_log_test to cover SVM
> >   KVM: selftests: Extend memstress to run on nested SVM
> 
> Lot's of feedback incoming, but no need for you to doing anything unless you
> disagree with something.  I have all the "requested" changes in a local branch,
> and will post v4 (probably next week).

Thanks a lot for taking care of this. No disagreements, just a couple of
comments/questions in the replies.