[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <30ae7206798d37f2887fc76f26a4c586fd7d9699.camel@intel.com>
Date: Thu, 23 Jan 2025 19:44:03 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "Li, Xiaoyao" <xiaoyao.li@...el.com>, "pbonzini@...hat.com"
<pbonzini@...hat.com>, "seanjc@...gle.com" <seanjc@...gle.com>
CC: "isaku.yamahata@...il.com" <isaku.yamahata@...il.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>, "Chatre, Reinette"
<reinette.chatre@...el.com>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "Huang, Kai" <kai.huang@...el.com>, "Zhao,
Yan Y" <yan.y.zhao@...el.com>, "tony.lindgren@...ux.intel.com"
<tony.lindgren@...ux.intel.com>
Subject: Re: [PATCH v2 24/25] KVM: x86: Introduce KVM_TDX_GET_CPUID
On Wed, 2025-01-22 at 15:43 +0800, Xiaoyao Li wrote:
> > Since we are not filtering by KVM supported features anymore, maybe just use
> > the
> > max leaf for the host CPU, like:
>
> host value is not matched with the value returned by TDX module.
> I.e., On my SPR machine, the boot_cpu_data.cpuid_level is 0x20, while
> TDX module returns 0x23. It at least fails to report the leaf 0x21 to
> userspace, which is a always valid leaf for TD guest.
Good point, we can use the cpuid level read from the TD.
Powered by blists - more mailing lists