[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4f54b07f-de1f-4b5b-89a7-a9d337b17ed9@oracle.com>
Date: Wed, 17 Dec 2025 10:11:45 -0800
From: ross.philipson@...cle.com
To: Randy Dunlap <rdunlap@...radead.org>, linux-kernel@...r.kernel.org,
x86@...nel.org, linux-integrity@...r.kernel.org,
linux-doc@...r.kernel.org, linux-crypto@...r.kernel.org,
kexec@...ts.infradead.org, linux-efi@...r.kernel.org,
iommu@...ts.linux.dev
Cc: dpsmith@...rtussolutions.com, tglx@...utronix.de, mingo@...hat.com,
bp@...en8.de, hpa@...or.com, dave.hansen@...ux.intel.com,
ardb@...nel.org, mjg59@...f.ucam.org,
James.Bottomley@...senpartnership.com, peterhuewe@....de,
jarkko@...nel.org, jgg@...pe.ca, luto@...capital.net,
nivedita@...m.mit.edu, herbert@...dor.apana.org.au,
davem@...emloft.net, corbet@....net, ebiederm@...ssion.com,
dwmw2@...radead.org, baolu.lu@...ux.intel.com,
kanth.ghatraju@...cle.com, andrew.cooper3@...rix.com,
trenchboot-devel@...glegroups.com, ross.philipson@...cle.com
Subject: Re: [PATCH v15 13/28] x86: Secure Launch Kconfig
On 12/15/25 7:20 PM, Randy Dunlap wrote:
>
>
> On 12/15/25 3:33 PM, Ross Philipson wrote:
>> Add a Kconfig option for compiling in/out the Secure Launch feature.
>> Secure Launch is controlled by a singel boolean on/off.
>>
>> Signed-off-by: Ross Philipson <ross.philipson@...cle.com>
>> ---
>> arch/x86/Kconfig | 14 ++++++++++++++
>> 1 file changed, 14 insertions(+)
>>
>> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
>> index fa3b616af03a..9404d207c420 100644
>> --- a/arch/x86/Kconfig
>> +++ b/arch/x86/Kconfig
>> @@ -1975,6 +1975,20 @@ config EFI_RUNTIME_MAP
>>
>> See also Documentation/ABI/testing/sysfs-firmware-efi-runtime-map.
>>
>> +config SECURE_LAUNCH
>> + bool "Secure Launch DRTM support"
>> + depends on X86_64 && X86_X2APIC && TCG_TIS && TCG_CRB
>> + select CRYPTO_LIB_SHA1
>> + select CRYPTO_LIB_SHA256
>> + help
>> + The Secure Launch feature allows a kernel to be launched directly
>> + through a vendor neutral DTRM (Dynamic Root of Trust for Measurement)
>
> DRTM
Thank you, will fix.
Ross
>
>> + solution, with Intel TXT being one example. The DRTM establishes an
>> + environment where the CPU measures the kernel image, employing the TPM,
>> + before starting it. Secure Launch then continues the measurement chain
>> + over kernel configuration information and other launch artifacts (e.g.
>> + any initramfs image).
>> +
>> source "kernel/Kconfig.hz"
>>
>> config ARCH_SUPPORTS_KEXEC
>
Powered by blists - more mailing lists