On Wed, Jul 23, 2025, Fuad Tabba wrote: > Ackerley Tng (1): > KVM: x86/mmu: Rename .private_max_mapping_level() to > .gmem_max_mapping_level() > > Fuad Tabba (15): > KVM: Rename CONFIG_KVM_PRIVATE_MEM to CONFIG_KVM_GUEST_MEMFD > KVM: Rename CONFIG_KVM_GENERIC_PRIVATE_MEM to > CONFIG_HAVE_KVM_ARCH_GMEM_POPULATE > KVM: Rename kvm_slot_can_be_private() to kvm_slot_has_gmem() > KVM: Fix comments that refer to slots_lock > KVM: Fix comment that refers to kvm uapi header path > KVM: x86: Enable KVM_GUEST_MEMFD for all 64-bit builds > KVM: guest_memfd: Add plumbing to host to map guest_memfd pages > KVM: guest_memfd: Track guest_memfd mmap support in memslot > KVM: arm64: Refactor user_mem_abort() > KVM: arm64: Handle guest_memfd-backed guest page faults > KVM: arm64: nv: Handle VNCR_EL2-triggered faults backed by guest_memfd > KVM: arm64: Enable support for guest_memfd backed memory > KVM: Allow and advertise support for host mmap() on guest_memfd files > KVM: selftests: Do not use hardcoded page sizes in guest_memfd test > KVM: selftests: guest_memfd mmap() test when mmap is supported > > Sean Christopherson (6): > KVM: x86: Have all vendor neutral sub-configs depend on KVM_X86, not > just KVM > KVM: x86: Select KVM_GENERIC_PRIVATE_MEM directly from > KVM_SW_PROTECTED_VM > KVM: x86: Select TDX's KVM_GENERIC_xxx dependencies iff > CONFIG_KVM_INTEL_TDX=y > KVM: x86/mmu: Hoist guest_memfd max level/order helpers "up" in mmu.c > KVM: x86/mmu: Enforce guest_memfd's max order when recovering > hugepages > KVM: x86/mmu: Extend guest_memfd's max mapping level to shared > mappings AFAICT, I've run out of things to complain about. :-D I say wait one more day just in case the peanut gallery comes alive, then spin a hopefully-final v17 early next week. Or holler if you want me to tidy things up and send v17, most of the goofs that necessitate v17 are mine :-)
