[RFC,v2,00/13] KVM: mm: fd-based approach for supporting KVM guest private memory

Message

Chao Peng Nov. 19, 2021, 1:47 p.m. UTC

This RFC series try to implement the fd-based KVM guest private memory
proposal described at [1] and an improved 'New Proposal' described at [2].

In general this patch series introduce fd-based memslot which provide
guest memory through fd[offset,size] instead of hva/size. The fd then
can be created from a supported memory filesystem like tmpfs/hugetlbfs,
etc which we refer as memory backing store. KVM and backing store
exchange some callbacks when such memslot gets created. At runtime KVM
will call into callbacks provided by backing store to get the pfn with
the fd+offset. Backing store will also call into KVM callbacks when
userspace fallocate/punch hole on fd to notify KVM to map/unmap second
MMU page tables.

Comparing to existing hva-based memslot, this new type of memslot allow
guest memory unmapped from host userspace like QEMU and even the kernel
itself, therefore reduce attack surface and bring some other benefits. 

Based on this fd-based memslot, we can build guest private memory that
is going to be used in confidential computing environments such as Intel
TDX and AMD SEV. When supported, the backing store can provide more
enforcement on the fd and KVM can use a single memslot to hold both
private and shared part of the guest memory. For more detailed
description please refer to [2].

Because this design introducing some callbacks between memory backing
store and KVM, and for private memory KVM relies on backing store to do
additonal enforcement and to tell if a address is private or shared,
I would like KVM/mm/fs people can have a look at this part.


[1]
https://lkml.kernel.org/kvm/[e-mail]/
[2]
https://lkml.kernel.org/linux-fsdevel/[e-mail]/

Thanks,
Chao
---
Chao Peng (12):
  KVM: Add KVM_EXIT_MEMORY_ERROR exit
  KVM: Extend kvm_userspace_memory_region to support fd based memslot
  KVM: Add fd-based memslot data structure and utils
  KVM: Implement fd-based memory using new memfd interfaces
  KVM: Register/unregister memfd backed memslot
  KVM: Handle page fault for fd based memslot
  KVM: Rename hva memory invalidation code to cover fd-based offset
  KVM: Introduce kvm_memfd_invalidate_range
  KVM: Match inode for invalidation of fd-based slot
  KVM: Add kvm_map_gfn_range
  KVM: Introduce kvm_memfd_fallocate_range
  KVM: Enable memfd based page invalidation/fallocate

Kirill A. Shutemov (1):
  mm/shmem: Introduce F_SEAL_GUEST

 arch/arm64/kvm/mmu.c               |  14 +--
 arch/mips/kvm/mips.c               |  14 +--
 arch/powerpc/include/asm/kvm_ppc.h |  28 ++---
 arch/powerpc/kvm/book3s.c          |  14 +--
 arch/powerpc/kvm/book3s_hv.c       |  14 +--
 arch/powerpc/kvm/book3s_pr.c       |  14 +--
 arch/powerpc/kvm/booke.c           |  14 +--
 arch/powerpc/kvm/powerpc.c         |  14 +--
 arch/riscv/kvm/mmu.c               |  14 +--
 arch/s390/kvm/kvm-s390.c           |  14 +--
 arch/x86/include/asm/kvm_host.h    |   6 +-
 arch/x86/kvm/Makefile              |   3 +-
 arch/x86/kvm/mmu/mmu.c             | 122 ++++++++++++++++++++-
 arch/x86/kvm/vmx/main.c            |   6 +-
 arch/x86/kvm/vmx/tdx.c             |   6 +-
 arch/x86/kvm/vmx/tdx_stubs.c       |   6 +-
 arch/x86/kvm/x86.c                 |  16 +--
 include/linux/kvm_host.h           |  58 ++++++++--
 include/linux/memfd.h              |  24 +++++
 include/linux/shmem_fs.h           |   9 ++
 include/uapi/linux/fcntl.h         |   1 +
 include/uapi/linux/kvm.h           |  27 +++++
 mm/memfd.c                         |  33 +++++-
 mm/shmem.c                         | 123 ++++++++++++++++++++-
 virt/kvm/kvm_main.c                | 165 +++++++++++++++++++++++------
 virt/kvm/memfd.c                   | 123 +++++++++++++++++++++
 26 files changed, 733 insertions(+), 149 deletions(-)
 create mode 100644 virt/kvm/memfd.c

Comments

Andy Lutomirski Dec. 3, 2021, 1:08 a.m. UTC | #1

On 11/19/21 05:47, Chao Peng wrote:
> This RFC series try to implement the fd-based KVM guest private memory
> proposal described at [1] and an improved 'New Proposal' described at [2].

I generally like this.  Thanks!