From: Chao Peng <chao.p.peng@linux.intel.com> To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, qemu-devel@nongnu.org Cc: Paolo Bonzini <pbonzini@redhat.com>, Jonathan Corbet <corbet@lwn.net>, Sean Christopherson <seanjc@google.com>, Vitaly Kuznetsov <vkuznets@redhat.com>, Wanpeng Li <wanpengli@tencent.com>, Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>, Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>, x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>, Hugh Dickins <hughd@google.com>, Jeff Layton <jlayton@kernel.org>, "J . Bruce Fields" <bfields@fieldses.org>, Andrew Morton <akpm@linux-foundation.org>, Yu Zhang <yu.c.zhang@linux.intel.com>, Chao Peng <chao.p.peng@linux.intel.com>, "Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>, luto@kernel.org, john.ji@intel.com, susie.li@intel.com, jun.nakajima@intel.com, dave.hansen@intel.com, ak@linux.intel.com, david@redhat.com Subject: [RFC v2 PATCH 00/13] KVM: mm: fd-based approach for supporting KVM guest private memory Date: Fri, 19 Nov 2021 21:47:26 +0800 [thread overview] Message-ID: <20211119134739.20218-1-chao.p.peng@linux.intel.com> (raw) 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/51a6f74f-6c05-74b9-3fd7-b7cd900fb8cc@redhat.com/ [2] https://lkml.kernel.org/linux-fsdevel/20211111141352.26311-1-chao.p.peng@linux.intel.com/ 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 -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Chao Peng <chao.p.peng@linux.intel.com> To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, qemu-devel@nongnu.org Cc: Wanpeng Li <wanpengli@tencent.com>, jun.nakajima@intel.com, david@redhat.com, "J . Bruce Fields" <bfields@fieldses.org>, dave.hansen@intel.com, "H . Peter Anvin" <hpa@zytor.com>, Chao Peng <chao.p.peng@linux.intel.com>, ak@linux.intel.com, Jonathan Corbet <corbet@lwn.net>, Joerg Roedel <joro@8bytes.org>, x86@kernel.org, Hugh Dickins <hughd@google.com>, Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>, luto@kernel.org, Thomas Gleixner <tglx@linutronix.de>, Vitaly Kuznetsov <vkuznets@redhat.com>, Jim Mattson <jmattson@google.com>, Sean Christopherson <seanjc@google.com>, susie.li@intel.com, Jeff Layton <jlayton@kernel.org>, john.ji@intel.com, Yu Zhang <yu.c.zhang@linux.intel.com>, Paolo Bonzini <pbonzini@redhat.com>, Andrew Morton <akpm@linux-foundation.org>, "Kirill A . Shutemov" <kirill.shutemov@linux.intel.com> Subject: [RFC v2 PATCH 00/13] KVM: mm: fd-based approach for supporting KVM guest private memory Date: Fri, 19 Nov 2021 21:47:26 +0800 [thread overview] Message-ID: <20211119134739.20218-1-chao.p.peng@linux.intel.com> (raw) 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/51a6f74f-6c05-74b9-3fd7-b7cd900fb8cc@redhat.com/ [2] https://lkml.kernel.org/linux-fsdevel/20211111141352.26311-1-chao.p.peng@linux.intel.com/ 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 -- 2.17.1
next reply other threads:[~2021-11-19 13:48 UTC|newest] Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-19 13:47 Chao Peng [this message] 2021-11-19 13:47 ` [RFC v2 PATCH 00/13] KVM: mm: fd-based approach for supporting KVM guest private memory Chao Peng 2021-11-19 13:47 ` [RFC v2 PATCH 01/13] mm/shmem: Introduce F_SEAL_GUEST Chao Peng 2021-11-19 13:47 ` Chao Peng 2021-11-19 13:51 ` David Hildenbrand 2021-11-19 13:51 ` David Hildenbrand 2021-11-22 13:59 ` Kirill A. Shutemov 2021-11-22 13:59 ` Kirill A. Shutemov 2021-11-19 15:19 ` Jason Gunthorpe 2021-11-19 15:19 ` Jason Gunthorpe 2021-11-19 15:39 ` David Hildenbrand 2021-11-19 15:39 ` David Hildenbrand 2021-11-19 16:00 ` Jason Gunthorpe 2021-11-19 16:00 ` Jason Gunthorpe 2021-11-22 9:26 ` David Hildenbrand 2021-11-22 9:26 ` David Hildenbrand 2021-11-22 13:31 ` Jason Gunthorpe 2021-11-22 13:31 ` Jason Gunthorpe 2021-11-22 13:35 ` David Hildenbrand 2021-11-22 13:35 ` David Hildenbrand 2021-11-22 14:01 ` Jason Gunthorpe 2021-11-22 14:01 ` Jason Gunthorpe 2021-11-22 14:57 ` David Hildenbrand 2021-11-22 14:57 ` David Hildenbrand 2021-11-22 15:09 ` Jason Gunthorpe 2021-11-22 15:09 ` Jason Gunthorpe 2021-11-22 15:15 ` David Hildenbrand 2021-11-22 15:15 ` David Hildenbrand 2021-11-19 19:18 ` Sean Christopherson 2021-11-19 19:47 ` Jason Gunthorpe 2021-11-19 19:47 ` Jason Gunthorpe 2021-11-19 22:21 ` Sean Christopherson 2021-11-19 23:33 ` Jason Gunthorpe 2021-11-19 23:33 ` Jason Gunthorpe 2021-11-20 1:23 ` Sean Christopherson 2021-11-21 0:05 ` Jason Gunthorpe 2021-11-21 0:05 ` Jason Gunthorpe 2021-11-23 9:06 ` Paolo Bonzini 2021-11-23 9:06 ` Paolo Bonzini 2021-11-23 14:33 ` Chao Peng 2021-11-23 14:33 ` Chao Peng 2021-11-23 15:20 ` David Hildenbrand 2021-11-23 15:20 ` David Hildenbrand 2021-11-23 17:17 ` Jason Gunthorpe 2021-11-23 17:17 ` Jason Gunthorpe 2021-11-23 8:54 ` Paolo Bonzini 2021-11-23 8:54 ` Paolo Bonzini 2021-12-03 1:11 ` Andy Lutomirski 2021-12-03 1:11 ` Andy Lutomirski 2021-11-19 13:47 ` [RFC v2 PATCH 02/13] KVM: Add KVM_EXIT_MEMORY_ERROR exit Chao Peng 2021-11-19 13:47 ` Chao Peng 2021-11-19 13:47 ` [RFC v2 PATCH 03/13] KVM: Extend kvm_userspace_memory_region to support fd based memslot Chao Peng 2021-11-19 13:47 ` Chao Peng 2021-11-19 13:47 ` [RFC v2 PATCH 04/13] KVM: Add fd-based memslot data structure and utils Chao Peng 2021-11-19 13:47 ` Chao Peng 2021-11-23 8:41 ` Paolo Bonzini 2021-11-23 8:41 ` Paolo Bonzini 2021-11-23 14:30 ` Chao Peng 2021-11-23 14:30 ` Chao Peng 2021-11-19 13:47 ` [RFC v2 PATCH 05/13] KVM: Implement fd-based memory using new memfd interfaces Chao Peng 2021-11-19 13:47 ` Chao Peng 2021-11-19 13:47 ` [RFC v2 PATCH 06/13] KVM: Register/unregister memfd backed memslot Chao Peng 2021-11-19 13:47 ` Chao Peng 2021-11-25 16:55 ` Steven Price 2021-11-25 16:55 ` Steven Price 2021-11-19 13:47 ` [RFC v2 PATCH 07/13] KVM: Handle page fault for fd based memslot Chao Peng 2021-11-19 13:47 ` Chao Peng 2021-11-20 1:55 ` Yao Yuan 2021-11-20 1:55 ` Yao Yuan 2021-11-22 9:18 ` Chao Peng 2021-11-22 9:18 ` Chao Peng 2021-11-19 13:47 ` [RFC v2 PATCH 08/13] KVM: Rename hva memory invalidation code to cover fd-based offset Chao Peng 2021-11-19 13:47 ` Chao Peng 2021-11-19 13:47 ` [RFC v2 PATCH 09/13] KVM: Introduce kvm_memfd_invalidate_range Chao Peng 2021-11-19 13:47 ` Chao Peng 2021-11-23 8:46 ` Paolo Bonzini 2021-11-23 8:46 ` Paolo Bonzini 2021-11-23 14:24 ` Chao Peng 2021-11-23 14:24 ` Chao Peng 2021-11-19 13:47 ` [RFC v2 PATCH 10/13] KVM: Match inode for invalidation of fd-based slot Chao Peng 2021-11-19 13:47 ` Chao Peng 2021-11-19 13:47 ` [RFC v2 PATCH 11/13] KVM: Add kvm_map_gfn_range Chao Peng 2021-11-19 13:47 ` Chao Peng 2021-11-19 13:47 ` [RFC v2 PATCH 12/13] KVM: Introduce kvm_memfd_fallocate_range Chao Peng 2021-11-19 13:47 ` Chao Peng 2021-11-19 13:47 ` [RFC v2 PATCH 13/13] KVM: Enable memfd based page invalidation/fallocate Chao Peng 2021-11-19 13:47 ` Chao Peng 2021-11-22 14:16 ` Kirill A. Shutemov 2021-11-22 14:16 ` Kirill A. Shutemov 2021-11-23 1:06 ` Chao Peng 2021-11-23 1:06 ` Chao Peng 2021-11-23 9:09 ` Paolo Bonzini 2021-11-23 9:09 ` Paolo Bonzini 2021-11-23 15:00 ` Chao Peng 2021-11-23 15:00 ` Chao Peng 2021-11-23 8:51 ` Paolo Bonzini 2021-11-23 8:51 ` Paolo Bonzini 2021-12-03 1:08 ` [RFC v2 PATCH 00/13] KVM: mm: fd-based approach for supporting KVM guest private memory Andy Lutomirski 2021-12-03 1:08 ` Andy Lutomirski
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20211119134739.20218-1-chao.p.peng@linux.intel.com \ --to=chao.p.peng@linux.intel.com \ --cc=ak@linux.intel.com \ --cc=akpm@linux-foundation.org \ --cc=bfields@fieldses.org \ --cc=bp@alien8.de \ --cc=corbet@lwn.net \ --cc=dave.hansen@intel.com \ --cc=david@redhat.com \ --cc=hpa@zytor.com \ --cc=hughd@google.com \ --cc=jlayton@kernel.org \ --cc=jmattson@google.com \ --cc=john.ji@intel.com \ --cc=joro@8bytes.org \ --cc=jun.nakajima@intel.com \ --cc=kirill.shutemov@linux.intel.com \ --cc=kvm@vger.kernel.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=luto@kernel.org \ --cc=mingo@redhat.com \ --cc=pbonzini@redhat.com \ --cc=qemu-devel@nongnu.org \ --cc=seanjc@google.com \ --cc=susie.li@intel.com \ --cc=tglx@linutronix.de \ --cc=vkuznets@redhat.com \ --cc=wanpengli@tencent.com \ --cc=x86@kernel.org \ --cc=yu.c.zhang@linux.intel.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.