From: Peter Xu <peterx@redhat.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>
Cc: David Hildenbrand <david@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: [PATCH] hostmem/shm: Allow shm memory backend serve as shared memory for coco-VMs
Date: Fri, 24 Oct 2025 11:52:28 -0400 [thread overview]
Message-ID: <aPugvDibWCyorBoW@x1.local> (raw)
In-Reply-To: <f59ba5d2-e205-46c7-90c0-8e02ab91f5ae@intel.com>
On Fri, Oct 24, 2025 at 08:51:35AM +0800, Xiaoyao Li wrote:
> On 9/12/2025 1:45 PM, Xiaoyao Li wrote:
> > On 8/14/2025 5:45 PM, Xiaoyao Li wrote:
> > > On 7/21/2025 2:52 PM, Xiaoyao Li wrote:
> > > > shm can surely serve as the shared memory for coco-VMs. But currently it
> > > > doesn't check the backend->guest_memfd to pass down the RAM_GUEST_MEMFD
> > > > flag. It leads to failure when creating coco-VMs (e.g., TDX guest) which
> > > > require private mmeory.
> > > >
> > > > Set and pass down RAM_GUEST_MEMFD when backend->guest_memfd is true, to
> > > > allow shm memory backend serve as shared memory for coco-VMs.
> > >
> > > ping...
> > >
> > > Paolo, will you merge it for QEMU 10.1? I think it's worth it.
> >
> > ping again.
>
> ping++,
>
> + Peter,
>
> Maybe you can queue it in case it gets missed from Paolo again?
Yep, queued now and I copied stable, let me know otherwise. Thanks.
--
Peter Xu
prev parent reply other threads:[~2025-10-24 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 6:52 [PATCH] hostmem/shm: Allow shm memory backend serve as shared memory for coco-VMs Xiaoyao Li
2025-07-21 7:50 ` Stefano Garzarella
2025-07-21 8:00 ` David Hildenbrand
2025-08-14 9:45 ` Xiaoyao Li
2025-09-12 5:45 ` Xiaoyao Li
2025-10-24 0:51 ` Xiaoyao Li
2025-10-24 15:52 ` Peter Xu [this message]
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=aPugvDibWCyorBoW@x1.local \
--to=peterx@redhat.com \
--cc=david@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--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.