From: Peter Xu <peterx@redhat.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Fabiano Rosas <farosas@suse.de>,
Chenyi Qiang <chenyi.qiang@intel.com>,
David Hildenbrand <david@redhat.com>,
Alexey Kardashevskiy <aik@amd.com>,
Juraj Marcin <jmarcin@redhat.com>
Subject: Re: [PATCH 2/8] kvm: Allow kvm_guest_memfd_supported for non-private use case
Date: Thu, 13 Nov 2025 16:05:55 -0500 [thread overview]
Message-ID: <aRZIM9baerzcuxOi@x1.local> (raw)
In-Reply-To: <9614d727-97bf-4a50-be13-6754952bec96@intel.com>
On Fri, Oct 24, 2025 at 10:30:19AM +0800, Xiaoyao Li wrote:
> On 10/24/2025 2:59 AM, Peter Xu wrote:
> > Guest-memfd is not 100% attached to private, it's a VM-specific memory
> > provider. Allow it to be created even without private attributes, for
> > example, when the VM can use the guest-memfd memory completely shared.
> >
> > Signed-off-by: Peter Xu <peterx@redhat.com>
> > ---
> > accel/kvm/kvm-all.c | 6 ++----
> > 1 file changed, 2 insertions(+), 4 deletions(-)
> >
> > diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
> > index f9254ae654..1425dfd8b3 100644
> > --- a/accel/kvm/kvm-all.c
> > +++ b/accel/kvm/kvm-all.c
> > @@ -2779,10 +2779,8 @@ static int kvm_init(AccelState *as, MachineState *ms)
> > }
> > kvm_supported_memory_attributes = kvm_vm_check_extension(s, KVM_CAP_MEMORY_ATTRIBUTES);
> > - kvm_guest_memfd_supported =
> > - kvm_vm_check_extension(s, KVM_CAP_GUEST_MEMFD) &&
> > - kvm_vm_check_extension(s, KVM_CAP_USER_MEMORY2) &&
> > - (kvm_supported_memory_attributes & KVM_MEMORY_ATTRIBUTE_PRIVATE);
> > + kvm_guest_memfd_supported = kvm_vm_check_extension(s, KVM_CAP_GUEST_MEMFD) &&
> > + kvm_vm_check_extension(s, KVM_CAP_USER_MEMORY2);
> > kvm_pre_fault_memory_supported = kvm_vm_check_extension(s, KVM_CAP_PRE_FAULT_MEMORY);
> > if (s->kernel_irqchip_split == ON_OFF_AUTO_AUTO) {
>
>
> The check on KVM_MEMORY_ATTRIBUTE_PRIVATE is dropped silently. But using
> guest memfd to serve as private memory does requires the support of
> KVM_MEMORY_ATTRIBUTE_PRIVATE.
>
> My version of the patch was
Your version looks good, I'll fetch yours to replace mine. Thanks.
--
Peter Xu
next prev parent reply other threads:[~2025-11-13 21:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 18:59 [PATCH 0/8] KVM/hostmem: Support in-place guest-memfd as VM backends Peter Xu
2025-10-23 18:59 ` [PATCH 1/8] linux-headers: Update to v6.18-rc2 Peter Xu
2025-10-23 18:59 ` [PATCH 2/8] kvm: Allow kvm_guest_memfd_supported for non-private use case Peter Xu
2025-10-24 2:30 ` Xiaoyao Li
2025-11-13 21:05 ` Peter Xu [this message]
2025-11-13 21:08 ` Peter Xu
2025-11-19 14:40 ` Xiaoyao Li
2025-10-23 18:59 ` [PATCH 3/8] kvm: Detect guest-memfd flags supported Peter Xu
2025-10-24 3:52 ` Xiaoyao Li
2025-11-13 21:15 ` Peter Xu
2025-11-13 21:19 ` Peter Xu
2025-11-19 14:44 ` Xiaoyao Li
2025-10-23 18:59 ` [PATCH 4/8] memory: Rename RAM_GUEST_MEMFD to RAM_GUEST_MEMFD_PRIVATE Peter Xu
2025-10-24 9:17 ` Xiaoyao Li
2025-11-13 21:25 ` Peter Xu
2025-11-19 14:45 ` Xiaoyao Li
2025-10-23 18:59 ` [PATCH 5/8] memory: Rename memory_region_has_guest_memfd() to *_private() Peter Xu
2025-10-23 18:59 ` [PATCH 6/8] ramblock: Rename guest_memfd to guest_memfd_private Peter Xu
2025-10-23 18:59 ` [PATCH 7/8] hostmem: " Peter Xu
2025-10-23 18:59 ` [PATCH 8/8] hostmem: Support in-place guest memfd to back a VM Peter Xu
2025-10-24 9:01 ` Xiaoyao Li
2025-10-24 15:22 ` Peter Xu
2025-10-27 5:24 ` Xiaoyao Li
2025-11-13 21:53 ` Peter Xu
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=aRZIM9baerzcuxOi@x1.local \
--to=peterx@redhat.com \
--cc=aik@amd.com \
--cc=chenyi.qiang@intel.com \
--cc=david@redhat.com \
--cc=farosas@suse.de \
--cc=jmarcin@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiaoyao.li@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: link
Be 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.