Re: [PATCH v3 11/49] physmem: Introduce ram_block_discard_guest_memfd_range()

[Xiaoyao Li]

On 3/20/2024 5:37 PM, David Hildenbrand wrote:
> On 20.03.24 09:39, Michael Roth wrote:
> > From: Xiaoyao Li <xiaoyao.li@intel.com>
> >
> > When memory page is converted from private to shared, the original
> > private memory is back'ed by guest_memfd. Introduce
> > ram_block_discard_guest_memfd_range() for discarding memory in
> > guest_memfd.
> >
> > Originally-from: Isaku Yamahata <isaku.yamahata@intel.com>
> > Codeveloped-by: Xiaoyao Li <xiaoyao.li@intel.com>
>
> "Co-developed-by"

Michael is using the patch from my TDX-QEMU v5 series[1]. I need to fix it.

> > Signed-off-by: Xiaoyao Li <xiaoyao.li@intel.com>
> > Reviewed-by: David Hildenbrand <david@redhat.com>
>
> Your SOB should go here.
>
> > ---
> > Changes in v5:
> > - Collect Reviewed-by from David;
> >
> > Changes in in v4:
> > - Drop ram_block_convert_range() and open code its implementation in the
> >    next Patch.
> >
> > Signed-off-by: Michael Roth <michael.roth@amd.com>
>
> I only received 3 patches from this series, and now I am confused: 
> changelog talks about v5 and this is "PATCH v3"

As above, because the guest_memfd patches in my TDX-QEMU v5[1] were 
directly picked for this series, so the change history says v5. They are 
needed by SEV-SNP as well.

I want to raise the question, how do we want to proceed with the guest 
memfd patches (patch 2 to 10 in [1])? Can they be merged separately 
before TDX/SNP patches?

> Please make sure to send at least the cover letter along (I might not 
> need the other 46 patches :D ).


[1] 
https://lore.kernel.org/qemu-devel/20240229063726.610065-1-xiaoyao.li@intel.com/