From: Ackerley Tng <ackerleytng@google.com>
To: Fuad Tabba <tabba@google.com>
Cc: kvm@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-mm@kvack.org, 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,
isaku.yamahata@intel.com, mic@digikod.net, vbabka@suse.cz,
vannapurve@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,
roypat@amazon.co.uk, shuah@kernel.org, hch@infradead.org,
jgg@nvidia.com, rientjes@google.com, jhubbard@nvidia.com,
fvdl@google.com, hughd@google.com, jthoughton@google.com,
peterx@redhat.com
Subject: Re: [PATCH v5 3/9] KVM: guest_memfd: Allow host to map guest_memfd() pages
Date: Thu, 06 Mar 2025 17:05:05 +0000 [thread overview]
Message-ID: <diqzikomt7i6.fsf@ackerleytng-ctop.c.googlers.com> (raw)
In-Reply-To: <CA+EHjTzOGuCvN91WS76Bx1dBOQNxv+Tqz=gTc85bVvjCrF0hyA@mail.gmail.com> (message from Fuad Tabba on Thu, 6 Mar 2025 08:48:41 +0000)
Fuad Tabba <tabba@google.com> writes:
> Hi Ackerley,
>
> On Thu, 6 Mar 2025 at 00:02, Ackerley Tng <ackerleytng@google.com> wrote:
>>
>> Fuad Tabba <tabba@google.com> writes:
>>
>> > <snip>
>> >
>> > +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)) {
>> > + switch (PTR_ERR(folio)) {
>> > + case -EAGAIN:
>> > + ret = VM_FAULT_RETRY;
>> > + break;
>> > + case -ENOMEM:
>> > + ret = VM_FAULT_OOM;
>> > + break;
>> > + default:
>> > + ret = VM_FAULT_SIGBUS;
>> > + break;
>> > + }
>> > + goto out_filemap;
>> > + }
>> > +
>> > + if (folio_test_hwpoison(folio)) {
>> > + ret = VM_FAULT_HWPOISON;
>> > + goto out_folio;
>> > + }
>> > +
>> > + /* Must be called with folio lock held, i.e., after kvm_gmem_get_folio() */
>> > + if (!kvm_gmem_offset_is_shared(vmf->vma->vm_file, vmf->pgoff)) {
>> > + ret = VM_FAULT_SIGBUS;
>> > + goto out_folio;
>> > + }
>> > +
>> > + /*
>> > + * Only private folios are marked as "guestmem" so far, and we never
>> > + * expect private folios at this point.
>> > + */
>>
>> I think this is not quite accurate.
>>
>> Based on my understanding and kvm_gmem_handle_folio_put() in this other
>> patch [1], only pages *in transition* from shared to private state are
>> marked "guestmem", although it is true that no private folios or folios
>> marked guestmem are expected here.
>
> Technically, pages in transition are private as far as the host is
> concerned. This doesn't say that _all_ private pages are marked as
> guestmem. It says that only private pages are marked as guestmem. It
> could be private and _not_ be marked as guestmem :)
True, didn't think of it this way!
>
> I probably should rephrase something along the lines of, "no shared
> folios would be marked as guestmem". How does that sound?
>
> Thanks,
> /fuad
>
Works for me, thank you!
>> > + 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_test_large(folio))) {
>> > + ret = VM_FAULT_SIGBUS;
>> > + goto out_folio;
>> > + }
>> > +
>> > + if (!folio_test_uptodate(folio)) {
>> > + clear_highpage(folio_page(folio, 0));
>> > + kvm_gmem_mark_prepared(folio);
>> > + }
>> > +
>> > + vmf->page = folio_file_page(folio, vmf->pgoff);
>> > +
>> > +out_folio:
>> > + if (ret != VM_FAULT_LOCKED) {
>> > + folio_unlock(folio);
>> > + folio_put(folio);
>> > + }
>> > +
>> > +out_filemap:
>> > + filemap_invalidate_unlock_shared(inode->i_mapping);
>> > +
>> > + return ret;
>> > +}
>> >
>> > <snip>
>>
>> [1] https://lore.kernel.org/all/20250117163001.2326672-7-tabba@google.com/
next prev parent reply other threads:[~2025-03-06 17:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 17:10 [PATCH v5 0/9] KVM: Mapping guest_memfd backed memory at the host for software protected VMs Fuad Tabba
2025-03-03 17:10 ` [PATCH v5 1/9] mm: Consolidate freeing of typed folios on final folio_put() Fuad Tabba
2025-03-04 8:45 ` Kirill A. Shutemov
2025-03-04 9:43 ` David Hildenbrand
2025-03-03 17:10 ` [PATCH v5 2/9] KVM: guest_memfd: Handle final folio_put() of guest_memfd pages Fuad Tabba
2025-03-07 17:04 ` Ackerley Tng
2025-03-10 10:50 ` Fuad Tabba
2025-03-10 14:23 ` Ackerley Tng
2025-03-10 14:35 ` Fuad Tabba
2025-03-03 17:10 ` [PATCH v5 3/9] KVM: guest_memfd: Allow host to map guest_memfd() pages Fuad Tabba
2025-03-04 8:58 ` Kirill A. Shutemov
2025-03-04 9:27 ` Fuad Tabba
2025-03-04 9:45 ` Kirill A. Shutemov
2025-03-04 9:52 ` Fuad Tabba
2025-03-06 0:01 ` Ackerley Tng
2025-03-06 8:48 ` Fuad Tabba
2025-03-06 17:05 ` Ackerley Tng [this message]
2025-03-06 22:46 ` Ackerley Tng
2025-03-07 8:57 ` Fuad Tabba
2025-03-07 1:53 ` James Houghton
2025-03-07 8:55 ` Fuad Tabba
2025-03-03 17:10 ` [PATCH v5 4/9] KVM: guest_memfd: Handle in-place shared memory as guest_memfd backed memory Fuad Tabba
2025-03-06 16:09 ` Ackerley Tng
2025-03-06 17:02 ` Fuad Tabba
2025-03-03 17:10 ` [PATCH v5 5/9] KVM: x86: Mark KVM_X86_SW_PROTECTED_VM as supporting guest_memfd shared memory Fuad Tabba
2025-03-03 17:10 ` [PATCH v5 6/9] KVM: arm64: Refactor user_mem_abort() calculation of force_pte Fuad Tabba
2025-03-06 10:46 ` Quentin Perret
2025-03-06 10:54 ` Fuad Tabba
2025-03-03 17:10 ` [PATCH v5 7/9] KVM: arm64: Handle guest_memfd()-backed guest page faults Fuad Tabba
2025-03-03 17:10 ` [PATCH v5 8/9] KVM: arm64: Enable mapping guest_memfd in arm64 Fuad Tabba
2025-03-03 17:10 ` [PATCH v5 9/9] KVM: guest_memfd: selftests: guest_memfd mmap() test when mapping is allowed 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=diqzikomt7i6.fsf@ackerleytng-ctop.c.googlers.com \
--to=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=peterx@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=roypat@amazon.co.uk \
--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=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