[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZsWF2UJmFdqlDmEs@tlindgre-MOBL1>
Date: Wed, 21 Aug 2024 09:14:49 +0300
From: Tony Lindgren <tony.lindgren@...ux.intel.com>
To: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
Cc: "binbin.wu@...ux.intel.com" <binbin.wu@...ux.intel.com>,
"seanjc@...gle.com" <seanjc@...gle.com>,
"Huang, Kai" <kai.huang@...el.com>,
"Li, Xiaoyao" <xiaoyao.li@...el.com>,
"isaku.yamahata@...il.com" <isaku.yamahata@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"pbonzini@...hat.com" <pbonzini@...hat.com>,
"Yamahata, Isaku" <isaku.yamahata@...el.com>
Subject: Re: [PATCH 09/25] KVM: TDX: Get system-wide info about TDX module on
initialization
On Wed, Aug 21, 2024 at 12:11:16AM +0000, Edgecombe, Rick P wrote:
> On Wed, 2024-08-14 at 14:18 +0800, Binbin Wu wrote:
> > > +#define KVM_TDX_CPUID_NO_SUBLEAF ((__u32)-1)
> > > +
> > > +struct kvm_tdx_cpuid_config {
> > > + __u32 leaf;
> > > + __u32 sub_leaf;
> > > + __u32 eax;
> > > + __u32 ebx;
> > > + __u32 ecx;
> > > + __u32 edx;
> > > +};
> >
> > I am wondering if there is any specific reason to define a new structure
> > instead of using 'struct kvm_cpuid_entry2'?
>
> GOod question. I don't think so.
I'll do a patch for this.
Regards,
Tony
Powered by blists - more mailing lists