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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3d62aeb993d9a81a64985a8354b87ffedd35514e.camel@intel.com>
Date: Thu, 17 Jul 2025 15:24:18 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "Li, Xiaoyao" <xiaoyao.li@...el.com>, "Annapurve, Vishal"
	<vannapurve@...gle.com>
CC: "kvm@...r.kernel.org" <kvm@...r.kernel.org>, "pbonzini@...hat.com"
	<pbonzini@...hat.com>, "seanjc@...gle.com" <seanjc@...gle.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] KVM: TDX: Don't report base TDVMCALLs

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@...el.com> 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@redhat.com/#t

But it didn't have those changes. They got added before it was sent upstream.
Possibly in response to this discussion, but I'm not sure:
https://lore.kernel.org/kvm/e6fedf41180a98068c0b410b628f14cb85cad93f.camel@intel.com/