[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250820132104.8633-1-nik.borisov@suse.com>
Date: Wed, 20 Aug 2025 16:21:04 +0300
From: Nikolay Borisov <nik.borisov@...e.com>
To: x86@...nel.org
Cc: dave.hansen@...ux.intel.comd,
linux-kernel@...r.kernel.org,
mhocko@...e.de,
Nikolay Borisov <nik.borisov@...e.com>
Subject: [PATCH] x86/tsx: Set default TSX mode to auto
The last known vulnerability concerning TSX was TAA (CVE-2019-11135) a
lot of time has passed since then and Intel has released a numerous
processor which do not have the TAA vulnerability (Cooper/Ice Lake,
Sapphire/Emerald/Granite Rappids) yet have TSX disable by default.
I believe having the default to AUTO rather than OFF strikes a good
balance between mitigation and reaping the benefits of the TSX feature.
So let's switch the default to AUTO.
Signed-off-by: Nikolay Borisov <nik.borisov@...e.com>
---
arch/x86/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 58d890fe2100..d1c4a8840d7c 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1810,7 +1810,7 @@ config ARCH_PKEY_BITS
choice
prompt "TSX enable mode"
depends on CPU_SUP_INTEL
- default X86_INTEL_TSX_MODE_OFF
+ default X86_INTEL_TSX_MODE_AUTO
help
Intel's TSX (Transactional Synchronization Extensions) feature
allows to optimize locking protocols through lock elision which
--
2.34.1
Powered by blists - more mailing lists