From: Patrick Roy <roypat@amazon.co.uk>
To: Fuad Tabba <tabba@google.com>, <kvm@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>, <linux-mm@kvack.org>
Cc: <pbonzini@redhat.com>, <chenhuacai@kernel.org>,
<mpe@ellerman.id.au>, <anup@brainfault.org>,
<paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
<aou@eecs.berkeley.edu>, <seanjc@google.com>,
<viro@zeniv.linux.org.uk>, <brauner@kernel.org>,
<willy@infradead.org>, <akpm@linux-foundation.org>,
<xiaoyao.li@intel.com>, <yilun.xu@intel.com>,
<chao.p.peng@linux.intel.com>, <jarkko@kernel.org>,
<amoorthy@google.com>, <dmatlack@google.com>,
<yu.c.zhang@linux.intel.com>, <isaku.yamahata@intel.com>,
<mic@digikod.net>, <vbabka@suse.cz>, <vannapurve@google.com>,
<ackerleytng@google.com>, <mail@maciej.szmigiero.name>,
<david@redhat.com>, <michael.roth@amd.com>,
<wei.w.wang@intel.com>, <liam.merwick@oracle.com>,
<isaku.yamahata@gmail.com>, <kirill.shutemov@linux.intel.com>,
<suzuki.poulose@arm.com>, <steven.price@arm.com>,
<quic_eberman@quicinc.com>, <quic_mnalajal@quicinc.com>,
<quic_tsoni@quicinc.com>, <quic_svaddagi@quicinc.com>,
<quic_cvanscha@quicinc.com>, <quic_pderrin@quicinc.com>,
<quic_pheragu@quicinc.com>, <catalin.marinas@arm.com>,
<james.morse@arm.com>, <yuzenghui@huawei.com>,
<oliver.upton@linux.dev>, <maz@kernel.org>, <will@kernel.org>,
<qperret@google.com>, <keirf@google.com>, <shuah@kernel.org>,
<hch@infradead.org>, <jgg@nvidia.com>, <rientjes@google.com>,
<jhubbard@nvidia.com>, <fvdl@google.com>, <hughd@google.com>,
<jthoughton@google.com>
Subject: Re: [RFC PATCH v2 03/11] KVM: guest_memfd: Allow host to map guest_memfd() pages
Date: Fri, 7 Feb 2025 16:45:26 +0000 [thread overview]
Message-ID: <0b1cc981-52e8-4f8f-846a-f19507e3a630@amazon.co.uk> (raw)
In-Reply-To: <20250129172320.950523-4-tabba@google.com>
Hi Fuad!
On Wed, 2025-01-29 at 17:23 +0000, Fuad Tabba wrote:
> Add support for mmap() and fault() for guest_memfd backed memory
> in the host for VMs that support in-place conversion between
> shared and private (shared memory). To that end, this patch adds
> the ability to check whether the VM type has that support, and
> only allows mapping its memory if that's the case.
>
> Additionally, this behavior is gated with a new configuration
> option, CONFIG_KVM_GMEM_SHARED_MEM.
>
> Signed-off-by: Fuad Tabba <tabba@google.com>
>
> ---
>
> This patch series will allow shared memory support for software
> VMs in x86. It will also introduce a similar VM type for arm64
> and allow shared memory support for that. In the future, pKVM
> will also support shared memory.
> ---
> include/linux/kvm_host.h | 11 ++++++
> virt/kvm/Kconfig | 4 +++
> virt/kvm/guest_memfd.c | 77 ++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 92 insertions(+)
>
> -snip-
>
> diff --git a/virt/kvm/guest_memfd.c b/virt/kvm/guest_memfd.c
> index 47a9f68f7b24..86441581c9ae 100644
> --- a/virt/kvm/guest_memfd.c
> +++ b/virt/kvm/guest_memfd.c
> @@ -307,7 +307,84 @@ static pgoff_t kvm_gmem_get_index(struct kvm_memory_slot *slot, gfn_t gfn)
> return gfn - slot->base_gfn + slot->gmem.pgoff;
> }
>
> +#ifdef CONFIG_KVM_GMEM_SHARED_MEM
> +static vm_fault_t kvm_gmem_fault(struct vm_fault *vmf)
> +{
> + struct inode *inode = file_inode(vmf->vma->vm_file);
> + struct folio *folio;
> + vm_fault_t ret = VM_FAULT_LOCKED;
> +
> + filemap_invalidate_lock_shared(inode->i_mapping);
> +
> + folio = kvm_gmem_get_folio(inode, vmf->pgoff);
> + if (IS_ERR(folio)) {
> + ret = VM_FAULT_SIGBUS;
> + goto out_filemap;
> + }
> +
> + if (folio_test_hwpoison(folio)) {
> + ret = VM_FAULT_HWPOISON;
> + goto out_folio;
> + }
> +
> + if (WARN_ON_ONCE(folio_test_guestmem(folio))) {
> + ret = VM_FAULT_SIGBUS;
> + goto out_folio;
> + }
> +
> + /* No support for huge pages. */
> + if (WARN_ON_ONCE(folio_nr_pages(folio) > 1)) {
> + ret = VM_FAULT_SIGBUS;
> + goto out_folio;
> + }
> +
> + if (!folio_test_uptodate(folio)) {
> + clear_highpage(folio_page(folio, 0));
> + folio_mark_uptodate(folio);
kvm_gmem_mark_prepared() instead of direct folio_mark_uptodate() here, I
think (in preparation of things like [1])? Noticed this while rebasing
my direct map removal series on top of this and wondering why mmap'd
folios sometimes didn't get removed (since it hooks mark_prepared()).
Best,
Patrick
[1]: https://lore.kernel.org/kvm/20241108155056.332412-1-pbonzini@redhat.com/
next prev parent reply other threads:[~2025-02-07 16:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 17:23 [RFC PATCH v2 00/11] KVM: Mapping guest_memfd backed memory at the host for software protected VMs Fuad Tabba
2025-01-29 17:23 ` [RFC PATCH v2 01/11] mm: Consolidate freeing of typed folios on final folio_put() Fuad Tabba
2025-01-29 17:23 ` [RFC PATCH v2 02/11] KVM: guest_memfd: Handle final folio_put() of guest_memfd pages Fuad Tabba
2025-01-30 17:16 ` David Hildenbrand
2025-01-31 9:02 ` Fuad Tabba
2025-01-29 17:23 ` [RFC PATCH v2 03/11] KVM: guest_memfd: Allow host to map guest_memfd() pages Fuad Tabba
2025-01-30 17:20 ` David Hildenbrand
2025-01-31 9:11 ` Fuad Tabba
2025-02-07 16:45 ` Patrick Roy [this message]
2025-02-10 8:33 ` Fuad Tabba
2025-01-29 17:23 ` [RFC PATCH v2 04/11] KVM: guest_memfd: Add KVM capability to check if guest_memfd is shared Fuad Tabba
2025-01-31 9:11 ` David Hildenbrand
2025-01-31 9:52 ` Fuad Tabba
2025-01-31 10:52 ` David Hildenbrand
2025-01-29 17:23 ` [RFC PATCH v2 05/11] KVM: guest_memfd: Handle in-place shared memory as guest_memfd backed memory Fuad Tabba
2025-01-29 17:23 ` [RFC PATCH v2 06/11] KVM: x86: Mark KVM_X86_SW_PROTECTED_VM as supporting guest_memfd shared memory Fuad Tabba
2025-01-29 17:23 ` [RFC PATCH v2 07/11] KVM: arm64: Refactor user_mem_abort() calculation of force_pte Fuad Tabba
2025-01-29 17:23 ` [RFC PATCH v2 08/11] KVM: arm64: Handle guest_memfd()-backed guest page faults Fuad Tabba
2025-01-29 17:23 ` [RFC PATCH v2 09/11] KVM: arm64: Introduce KVM_VM_TYPE_ARM_SW_PROTECTED machine type Fuad Tabba
2025-01-29 17:23 ` [RFC PATCH v2 10/11] KVM: arm64: Enable mapping guest_memfd in arm64 Fuad Tabba
2025-01-29 17:23 ` [RFC PATCH v2 11/11] KVM: guest_memfd: selftests: guest_memfd mmap() test when mapping is allowed Fuad Tabba
2025-01-30 16:50 ` [RFC PATCH v2 00/11] KVM: Mapping guest_memfd backed memory at the host for software protected VMs David Hildenbrand
2025-01-30 16:57 ` Fuad Tabba
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=0b1cc981-52e8-4f8f-846a-f19507e3a630@amazon.co.uk \
--to=roypat@amazon.co.uk \
--cc=ackerleytng@google.com \
--cc=akpm@linux-foundation.org \
--cc=amoorthy@google.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=brauner@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chao.p.peng@linux.intel.com \
--cc=chenhuacai@kernel.org \
--cc=david@redhat.com \
--cc=dmatlack@google.com \
--cc=fvdl@google.com \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=isaku.yamahata@gmail.com \
--cc=isaku.yamahata@intel.com \
--cc=james.morse@arm.com \
--cc=jarkko@kernel.org \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=jthoughton@google.com \
--cc=keirf@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=liam.merwick@oracle.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mail@maciej.szmigiero.name \
--cc=maz@kernel.org \
--cc=mic@digikod.net \
--cc=michael.roth@amd.com \
--cc=mpe@ellerman.id.au \
--cc=oliver.upton@linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pbonzini@redhat.com \
--cc=qperret@google.com \
--cc=quic_cvanscha@quicinc.com \
--cc=quic_eberman@quicinc.com \
--cc=quic_mnalajal@quicinc.com \
--cc=quic_pderrin@quicinc.com \
--cc=quic_pheragu@quicinc.com \
--cc=quic_svaddagi@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=rientjes@google.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=vannapurve@google.com \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
--cc=wei.w.wang@intel.com \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=xiaoyao.li@intel.com \
--cc=yilun.xu@intel.com \
--cc=yu.c.zhang@linux.intel.com \
--cc=yuzenghui@huawei.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox