Re: [PATCH] KVM: TDX: Don't report base TDVMCALLs

[Paolo Bonzini]

On 7/17/25 17:24, Edgecombe, Rick P wrote:
> On Thu, 2025-07-17 at 05:25 -0700, Vishal Annapurve wrote:
> > On Wed, Jul 16, 2025 at 7:28 PM Xiaoyao Li <xiaoyao.li@xxxxxxxxx> wrote:
> > > diff --git a/arch/x86/kvm/vmx/tdx.c b/arch/x86/kvm/vmx/tdx.c
> > > index f31ccdeb905b..ea1261ca805f 100644
> > > --- a/arch/x86/kvm/vmx/tdx.c
> > > +++ b/arch/x86/kvm/vmx/tdx.c
> > > @@ -173,7 +173,6 @@ static void td_init_cpuid_entry2(struct kvm_cpuid_entry2 *entry, unsigned char i
> > >           tdx_clear_unsupported_cpuid(entry);
> > >    }
> > >
> > > -#define TDVMCALLINFO_GET_QUOTE                         BIT(0)
> > >    #define TDVMCALLINFO_SETUP_EVENT_NOTIFY_INTERRUPT      BIT(1)
> >
> > I am struggling to find the patch that adds support for
> > TDVMCALLINFO_SETUP_EVENT_NOTIFY_INTERRUPT. Can you help point out the
> > series that adds this support?
>
> This was the last version of the series posted:
> https://lore.kernel.org/kvm/20250619180159.187358-1-pbonzini@xxxxxxxxxx/#t

Yep, I didn't send the patches for SetupEventNotifyInterrupt to the KVM 
mailing list.

I hadn't even noticed until now that I hadn't sent them because, when I 
came back from vacation, I found the matching QEMU patches in my inbox. 
So when git reported them to be in the next pull request I didn't think 
of double checking.  Of course the blame is mine---thanks Xiaoyao for 
writing the QEMU side.

They are:
- commit 28224ef02b56fceee2c161fe2a49a0bb197e44f5
  KVM: TDX: Report supported optional TDVMCALLs in TDX capabilities

- commit 4580dbef5ce0f95a4bd8ac2d007bc4fbf1539332
  KVM: TDX: Exit to userspace for SetupEventNotifyInterrupt

Sorry about that.

Paolo