[PATCH v5 03/12] x86: Secure Launch Kconfig

[Ross Philipson <ross.philipson@oracle.com>]

Initial bits to bring in Secure Launch functionality. Add Kconfig
options for compiling in/out the Secure Launch code.

Signed-off-by: Ross Philipson <ross.philipson@oracle.com>
---
 arch/x86/Kconfig | 34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 9f5bd41..3f69aeb 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1983,6 +1983,40 @@ config EFI_MIXED
 
 	   If unsure, say N.
 
+config SECURE_LAUNCH
+	bool "Secure Launch support"
+	default n
+	depends on X86_64 && X86_X2APIC
+	help
+	   The Secure Launch feature allows a kernel to be loaded
+	   directly through an Intel TXT measured launch. Intel TXT
+	   establishes a Dynamic Root of Trust for Measurement (DRTM)
+	   where the CPU measures the kernel image. This feature then
+	   continues the measurement chain over kernel configuration
+	   information and init images.
+
+config SECURE_LAUNCH_ALT_DLME_AUTHORITY
+	bool "Secure Launch Alternate DLME Authority PCR"
+	default n
+	depends on SECURE_LAUNCH
+	help
+	   As the DLME environment, Secure Launch by default measures
+	   the configuration information as the DLME Authority into
+	   PCR18. This feature allows separating these measurements
+	   into the TCG DRTM specification PCR (PCR.DLME_AUTHORITY),
+	   PCR19.
+
+config SECURE_LAUNCH_ALT_DLME_DETAIL
+	bool "Secure Launch Alternate DLME Detail PCR"
+	default n
+	depends on SECURE_LAUNCH
+	help
+	   As the DLME environment, Secure Launch by default measures
+	   the image data like any external initrd as a DRTM Detail
+	   into PCR17. This feature allows separating these
+	   measurements into the Secure Launch's Detail PCR
+	   (PCR.DLME_DETAIL), PCR20.
+
 source "kernel/Kconfig.hz"
 
 config KEXEC
-- 
1.8.3.1