[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y3vyNDpcR5+nScdw@zn.tnic>
Date: Mon, 21 Nov 2022 22:48:36 +0100
From: Borislav Petkov <bp@...en8.de>
To: Dave Hansen <dave.hansen@...el.com>
Cc: Dexuan Cui <decui@...rosoft.com>, ak@...ux.intel.com,
arnd@...db.de, brijesh.singh@....com, dan.j.williams@...el.com,
dave.hansen@...ux.intel.com, haiyangz@...rosoft.com, hpa@...or.com,
jane.chu@...cle.com, kirill.shutemov@...ux.intel.com,
kys@...rosoft.com, linux-arch@...r.kernel.org,
linux-hyperv@...r.kernel.org, luto@...nel.org, mingo@...hat.com,
peterz@...radead.org, rostedt@...dmis.org,
sathyanarayanan.kuppuswamy@...ux.intel.com, seanjc@...gle.com,
tglx@...utronix.de, tony.luck@...el.com, wei.liu@...nel.org,
x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/6] x86/hyperv: Add hv_isolation_type_tdx() to detect
TDX guests
On Mon, Nov 21, 2022 at 01:01:45PM -0800, Dave Hansen wrote:
> On 11/21/22 11:51, Dexuan Cui wrote:
> > + switch (hv_get_isolation_type()) {
> > + case HV_ISOLATION_TYPE_VBS:
> > + case HV_ISOLATION_TYPE_SNP:
> > cc_set_vendor(CC_VENDOR_HYPERV);
> > + break;
> > +
> > + case HV_ISOLATION_TYPE_TDX:
> > + static_branch_enable(&isolation_type_tdx);
> > + break;
>
> This makes zero logical sense to me.
>
> Running on Hyper-V, a HV_ISOLATION_TYPE_SNP is CC_VENDOR_HYPERV, but a
> HV_ISOLATION_TYPE_TDX guest is *NOT* CC_VENDOR_HYPERV?
https://lore.kernel.org/r/Y3uTK3rBV6eXSJnC@zn.tnic
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists