From: Xiaoyao Li <xiaoyao.li@intel.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/3] kvm: guest_memfd enhancement and fix for KVM_SET_USER_MEMORY_REGION2
Date: Fri, 12 Sep 2025 13:47:04 +0800 [thread overview]
Message-ID: <807f9e9c-40b0-46fa-b92e-81cde9f301a6@intel.com> (raw)
In-Reply-To: <20250728115707.1374614-1-xiaoyao.li@intel.com>
On 7/28/2025 7:57 PM, Xiaoyao Li wrote:
> Patch 1 changes to check guest memfd CAP on VM instance.
>
> Patch 2 is a fix for KVM_SET_USER_MEMORY_REGION2.
>
> Patch 3 is an enhancement for guest_memfd_offset.
Gentle ping.
> ---
> Changes in v2:
> - Collect R-B tags;
> - Use {} to zero out the struct instead of memset() in patch2;
> - Initialize guest_memfd_offset at the original source in patch3;
>
> Xiaoyao Li (3):
> accel/kvm: Switch to check KVM_CAP_GUEST_MEMFD and
> KVM_CAP_USER_MEMORY2 on VM
> accel/kvm: Zero out mem explicitly in kvm_set_user_memory_region()
> accel/kvm: Set guest_memfd_offset to non-zero value only when
> guest_memfd is valid
>
> accel/kvm/kvm-all.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
next prev parent reply other threads:[~2025-09-12 5:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 11:57 [PATCH v2 0/3] kvm: guest_memfd enhancement and fix for KVM_SET_USER_MEMORY_REGION2 Xiaoyao Li
2025-07-28 11:57 ` [PATCH v2 1/3] accel/kvm: Switch to check KVM_CAP_GUEST_MEMFD and KVM_CAP_USER_MEMORY2 on VM Xiaoyao Li
2025-07-28 11:57 ` [PATCH v2 2/3] accel/kvm: Zero out mem explicitly in kvm_set_user_memory_region() Xiaoyao Li
2025-07-28 11:57 ` [PATCH v2 3/3] accel/kvm: Set guest_memfd_offset to non-zero value only when guest_memfd is valid Xiaoyao Li
2025-09-12 5:47 ` Xiaoyao Li [this message]
2025-09-13 4:35 ` [PATCH v2 0/3] kvm: guest_memfd enhancement and fix for KVM_SET_USER_MEMORY_REGION2 Paolo Bonzini
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=807f9e9c-40b0-46fa-b92e-81cde9f301a6@intel.com \
--to=xiaoyao.li@intel.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).