[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d5f95b6b-df7f-416f-14c0-b4e284125d2a@intel.com>
Date: Mon, 21 Nov 2022 13:01:45 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Dexuan Cui <decui@...rosoft.com>, ak@...ux.intel.com,
arnd@...db.de, bp@...en8.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
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/6] x86/hyperv: Add hv_isolation_type_tdx() to detect TDX
guests
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?
Powered by blists - more mailing lists