Add INTEL_TDX_GUEST config option to selectively compile
TDX guest support.
Signed-off-by: Kuppuswamy Sathyanarayanan <[email protected]>
Reviewed-by: Andi Kleen <[email protected]>
Reviewed-by: Tony Luck <[email protected]>
---
Changes since v5:
* None
Changes since v4:
* None
Changes since v3:
* Removed PARAVIRT_XL from dependency list.
* Fixed typo in help content.
arch/x86/Kconfig | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index de58e0a5df50..ab0e7c346c44 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -865,6 +865,20 @@ config ACRN_GUEST
IOT with small footprint and real-time features. More details can be
found in https://projectacrn.org/.
+config INTEL_TDX_GUEST
+ bool "Intel Trusted Domain eXtensions Guest Support"
+ depends on X86_64 && CPU_SUP_INTEL && PARAVIRT
+ depends on SECURITY
+ select X86_X2APIC
+ select SECURITY_LOCKDOWN_LSM
+ help
+ Provide support for running in a trusted domain on Intel processors
+ equipped with Trusted Domain eXtensions. TDX is a new Intel
+ technology that extends VMX and Memory Encryption with a new kind of
+ virtual machine guest called Trust Domain (TD). A TD is designed to
+ run in a CPU mode that protects the confidentiality of TD memory
+ contents and the TD’s CPU state from other software, including VMM.
+
endif #HYPERVISOR_GUEST
source "arch/x86/Kconfig.cpu"
--
2.25.1
On Fri, Sep 03, 2021 at 10:28:03AM -0700, Kuppuswamy Sathyanarayanan wrote:
> +config INTEL_TDX_GUEST
> + bool "Intel Trusted Domain eXtensions Guest Support"
> + depends on X86_64 && CPU_SUP_INTEL && PARAVIRT
> + depends on SECURITY
> + select X86_X2APIC
> + select SECURITY_LOCKDOWN_LSM
> + help
> + Provide support for running in a trusted domain on Intel processors
> + equipped with Trusted Domain eXtensions. TDX is a new Intel
Nit: the word 'new' in this description will not age well, you should
consider removing it.
Regards,
Joerg
On 9/28/21 4:37 AM, Joerg Roedel wrote:
> Nit: the word 'new' in this description will not age well, you should
> consider removing it.
Yes. I will remove it.
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer