>-----Original Message-----
>From: Daniel P. Berrangé <berrange@redhat.com>
>Subject: Re: [PATCH v4 00/23] LIBVIRT: X86: TDX support
>
>FYI, QEMU soft freeze is next week, and rc0 release
>is Jul 22nd. I proposed we merge this series once
>the QEMU rc0 release is out, so this is likely ready
>for the libvirt August 1st release.

After QEMU rc0 release and before this merge, should I send a v5
with test data update from rc0 release?

Should I send a test data update for each 10.1.0-rcX release or only 10.1.0 release?

Thanks
Zhenzhong

On Fri, Jul 11, 2025 at 06:23:46 +0000, Duan, Zhenzhong wrote:
> 
> 
> >-----Original Message-----
> >From: Daniel P. Berrangé <berrange@redhat.com>
> >Subject: Re: [PATCH v4 00/23] LIBVIRT: X86: TDX support
> >
> >FYI, QEMU soft freeze is next week, and rc0 release
> >is Jul 22nd. I proposed we merge this series once
> >the QEMU rc0 release is out, so this is likely ready
> >for the libvirt August 1st release.
> 
> After QEMU rc0 release and before this merge, should I send a v5
> with test data update from rc0 release?
> 
> Should I send a test data update for each 10.1.0-rcX release or only 10.1.0 release?

It's okay to just update the caps to the final release state once it's
out.

You can, if you want, send an updated/replacement version of the patch
adding the caps before it will be pushed. Or perhaps if something
related to TDX changed. But that's extra work which is not necessary in
any way. The most of the changes are tracked by the default variant of
the test.

>-----Original Message-----
>From: Peter Krempa <pkrempa@redhat.com>
>Subject: Re: [PATCH v4 00/23] LIBVIRT: X86: TDX support
>
>On Fri, Jul 11, 2025 at 06:23:46 +0000, Duan, Zhenzhong wrote:
>>
>>
>> >-----Original Message-----
>> >From: Daniel P. Berrangé <berrange@redhat.com>
>> >Subject: Re: [PATCH v4 00/23] LIBVIRT: X86: TDX support
>> >
>> >FYI, QEMU soft freeze is next week, and rc0 release
>> >is Jul 22nd. I proposed we merge this series once
>> >the QEMU rc0 release is out, so this is likely ready
>> >for the libvirt August 1st release.
>>
>> After QEMU rc0 release and before this merge, should I send a v5
>> with test data update from rc0 release?
>>
>> Should I send a test data update for each 10.1.0-rcX release or only 10.1.0
>release?
>
>It's okay to just update the caps to the final release state once it's
>out.
>
>You can, if you want, send an updated/replacement version of the patch
>adding the caps before it will be pushed. Or perhaps if something
>related to TDX changed. But that's extra work which is not necessary in
>any way. The most of the changes are tracked by the default variant of
>the test.

Clear.

Thanks
Zhenzhong