[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <16ea75a9-8c94-4665-ae04-32d08aa4ebb2@intel.com>
Date: Thu, 9 Nov 2023 08:25:04 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Jeremi Piotrowski <jpiotrowski@...ux.microsoft.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
linux-kernel@...r.kernel.org,
Michael Kelley <mhklinux@...look.com>,
Dexuan Cui <decui@...rosoft.com>
Cc: linux-hyperv@...r.kernel.org, stefan.bader@...onical.com,
tim.gardner@...onical.com, roxana.nicolescu@...onical.com,
cascardo@...onical.com, kys@...rosoft.com, haiyangz@...rosoft.com,
wei.liu@...nel.org, kirill.shutemov@...ux.intel.com,
sashal@...nel.org
Subject: Re: [PATCH] x86/mm: Check cc_vendor when printing memory encryption
info
On 11/9/23 08:14, Jeremi Piotrowski wrote:
...
> pr_info("Memory Encryption Features active:");
>
> - if (cpu_feature_enabled(X86_FEATURE_TDX_GUEST)) {
> + if (cc_vendor == CC_VENDOR_INTEL) {
> pr_cont(" Intel TDX\n");
> return;
> }
Why aren't these guests setting X86_FEATURE_TDX_GUEST?
Powered by blists - more mailing lists