]> www.infradead.org Git - users/hch/configfs.git/commit
KVM: guest_memfd: Add interface for populating gmem pages with user data
authorPaolo Bonzini <pbonzini@redhat.com>
Wed, 14 Feb 2024 17:09:06 +0000 (12:09 -0500)
committerPaolo Bonzini <pbonzini@redhat.com>
Fri, 10 May 2024 17:11:47 +0000 (13:11 -0400)
commit1f6c06b177513e8a47c43e95d1985dbd9cff3ddd
tree992042292ec1dbf0ae727acbbf20cc6baa3da2d9
parent17573fd971f9e31ddee420eca8359ceff87e9e51
KVM: guest_memfd: Add interface for populating gmem pages with user data

During guest run-time, kvm_arch_gmem_prepare() is issued as needed to
prepare newly-allocated gmem pages prior to mapping them into the guest.
In the case of SEV-SNP, this mainly involves setting the pages to
private in the RMP table.

However, for the GPA ranges comprising the initial guest payload, which
are encrypted/measured prior to starting the guest, the gmem pages need
to be accessed prior to setting them to private in the RMP table so they
can be initialized with the userspace-provided data. Additionally, an
SNP firmware call is needed afterward to encrypt them in-place and
measure the contents into the guest's launch digest.

While it is possible to bypass the kvm_arch_gmem_prepare() hooks so that
this handling can be done in an open-coded/vendor-specific manner, this
may expose more gmem-internal state/dependencies to external callers
than necessary. Try to avoid this by implementing an interface that
tries to handle as much of the common functionality inside gmem as
possible, while also making it generic enough to potentially be
usable/extensible for TDX as well.

Suggested-by: Sean Christopherson <seanjc@google.com>
Signed-off-by: Michael Roth <michael.roth@amd.com>
Co-developed-by: Michael Roth <michael.roth@amd.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
include/linux/kvm_host.h
virt/kvm/guest_memfd.c