[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aBqlkz1bqhu-9toV@google.com>
Date: Tue, 6 May 2025 17:13:07 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: James Houghton <jthoughton@...gle.com>
Cc: Paolo Bonzini <pbonzini@...hat.com>, Jonathan Corbet <corbet@....net>, Marc Zyngier <maz@...nel.org>,
Oliver Upton <oliver.upton@...ux.dev>, Yan Zhao <yan.y.zhao@...el.com>,
Nikita Kalyazin <kalyazin@...zon.com>, Anish Moorthy <amoorthy@...gle.com>,
Peter Gonda <pgonda@...gle.com>, Peter Xu <peterx@...hat.com>,
David Matlack <dmatlack@...gle.com>, wei.w.wang@...el.com, kvm@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.linux.dev
Subject: Re: [PATCH v2 00/13] KVM: Introduce KVM Userfault
On Thu, Jan 09, 2025, James Houghton wrote:
> KVM: Add KVM_MEM_USERFAULT memslot flag and bitmap
> KVM: Add KVM_MEMORY_EXIT_FLAG_USERFAULT
> KVM: Allow late setting of KVM_MEM_USERFAULT on guest_memfd memslot
> KVM: Advertise KVM_CAP_USERFAULT in KVM_CHECK_EXTENSION
> KVM: x86/mmu: Add support for KVM_MEM_USERFAULT
> KVM: arm64: Add support for KVM_MEM_USERFAULT
> KVM: selftests: Fix vm_mem_region_set_flags docstring
> KVM: selftests: Fix prefault_mem logic
> KVM: selftests: Add va_start/end into uffd_desc
> KVM: selftests: Add KVM Userfault mode to demand_paging_test
> KVM: selftests: Inform set_memory_region_test of KVM_MEM_USERFAULT
> KVM: selftests: Add KVM_MEM_USERFAULT + guest_memfd toggle tests
> KVM: Documentation: Add KVM_CAP_USERFAULT and KVM_MEM_USERFAULT
> details
>
> Documentation/virt/kvm/api.rst | 33 +++-
> arch/arm64/kvm/Kconfig | 1 +
> arch/arm64/kvm/mmu.c | 26 +++-
> arch/x86/kvm/Kconfig | 1 +
> arch/x86/kvm/mmu/mmu.c | 27 +++-
> arch/x86/kvm/mmu/mmu_internal.h | 20 ++-
> arch/x86/kvm/x86.c | 36 +++--
> include/linux/kvm_host.h | 19 ++-
> include/uapi/linux/kvm.h | 6 +-
> .../selftests/kvm/demand_paging_test.c | 145 ++++++++++++++++--
> .../testing/selftests/kvm/include/kvm_util.h | 5 +
> .../selftests/kvm/include/userfaultfd_util.h | 2 +
> tools/testing/selftests/kvm/lib/kvm_util.c | 42 ++++-
> .../selftests/kvm/lib/userfaultfd_util.c | 2 +
> .../selftests/kvm/set_memory_region_test.c | 33 ++++
> virt/kvm/Kconfig | 3 +
> virt/kvm/kvm_main.c | 54 ++++++-
> 17 files changed, 419 insertions(+), 36 deletions(-)
I didn't look at the selftests changes, but nothing in this series scares me. We
bikeshedded most of this death this in the "exit on missing" series, so for me at
least, the only real question is whether or not we want to add the uAPI. AFAIK,
this is best proposal for post-copy guest_memfd support (and not just because it's
the only proposal :-D).
So... yes?
Attached are a variation on the series using the common "struct kvm_page_fault"
idea. The documentation change could be squashed with the final enablement patch.
Compile tested only. I would not be the least bit surprised if I completely
butchered something.
View attachment "0001-KVM-x86-mmu-Move-struct-kvm_page_fault-definition-to.patch" of type "text/x-diff" (5055 bytes)
View attachment "0002-KVM-arm64-Add-struct-kvm_page_fault-to-gather-common.patch" of type "text/x-diff" (5302 bytes)
View attachment "0003-KVM-arm64-x86-Require-struct-kvm_page_fault-for-memo.patch" of type "text/x-diff" (6452 bytes)
View attachment "0004-KVM-Add-common-infrastructure-for-KVM-Userfaults.patch" of type "text/x-diff" (5764 bytes)
View attachment "0005-KVM-x86-Add-support-for-KVM-userfault-exits.patch" of type "text/x-diff" (3085 bytes)
View attachment "0006-KVM-arm64-Add-support-for-KVM-userfault-exits.patch" of type "text/x-diff" (2129 bytes)
View attachment "0007-KVM-Enable-and-advertise-support-for-KVM-userfault-e.patch" of type "text/x-diff" (1882 bytes)
Powered by blists - more mailing lists