[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <971f158b-f28a-6c1f-c37c-fe67134d737c@intel.com>
Date: Thu, 8 Jun 2023 16:56:49 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Kai Huang <kai.huang@...el.com>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org
Cc: linux-mm@...ck.org, kirill.shutemov@...ux.intel.com,
tony.luck@...el.com, peterz@...radead.org, tglx@...utronix.de,
seanjc@...gle.com, pbonzini@...hat.com, david@...hat.com,
dan.j.williams@...el.com, rafael.j.wysocki@...el.com,
ying.huang@...el.com, reinette.chatre@...el.com,
len.brown@...el.com, ak@...ux.intel.com, isaku.yamahata@...el.com,
chao.gao@...el.com, sathyanarayanan.kuppuswamy@...ux.intel.com,
bagasdotme@...il.com, sagis@...gle.com, imammedo@...hat.com
Subject: Re: [PATCH v11 20/20] Documentation/x86: Add documentation for TDX
host support
On 6/4/23 07:27, Kai Huang wrote:
> +There is no CPUID or MSR to detect the TDX module. The kernel detects it
> +by initializing it.
Is this really what you want to say?
If the module is there, SEAMCALL works. If not, it doesn't. The module
is assumed to be there when SEAMCALL works. Right?
Yeah, that first SEAMCALL is probably an initialization call, but feel
like that's beside the point.
Powered by blists - more mailing lists