From: Chanho Min <chanho.min@lge.com>
To: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Gunho Lee <gunho.lee@lge.com>,
Chanho Min <chanho.min@lge.com>
Subject: [PATCH] arm64: set MITIGATE_SPECTRE_BRANCH_HISTORY to n by default
Date: Tue, 16 Jul 2024 17:51:36 +0900 [thread overview]
Message-ID: <20240716085136.4160-1-chanho.min@lge.com> (raw)
lmbench shows 25% performance regression after MITIGATE_SPECTRE_BRANCH_HISTORY
is enabled. This performance drop may be more significant than mitigating
the spectre-BHB. This patch changes this security option to disable by default
and makes it selectable.
- lat_syscall result with MITIGATE_SPECTRE_BRANCH_HISTORY enabled (cortex-a78)
write call 0.2777 0.2810 0.2824 0.280367
read call 0.3435 0.3452 0.3443 0.344333
- lat_syscall result with MITIGATE_SPECTRE_BRANCH_HISTORY disabled (cortex-a78)
write call 0.2101 0.2117 0.2116 0.2111
read call 0.2732 0.2744 0.2763 0.274633
Signed-off-by: Chanho Min <chanho.min@lge.com>
---
arch/arm64/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 5d91259ee7b5..be76f425c060 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -1626,7 +1626,7 @@ config UNMAP_KERNEL_AT_EL0
config MITIGATE_SPECTRE_BRANCH_HISTORY
bool "Mitigate Spectre style attacks against branch history" if EXPERT
- default y
+ default n
help
Speculation attacks against some high-performance processors can
make use of branch history to influence future speculation.
--
2.17.1
next reply other threads:[~2024-07-16 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 8:51 Chanho Min [this message]
2024-07-16 9:03 ` [PATCH] arm64: set MITIGATE_SPECTRE_BRANCH_HISTORY to n by default Will Deacon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240716085136.4160-1-chanho.min@lge.com \
--to=chanho.min@lge.com \
--cc=catalin.marinas@arm.com \
--cc=gunho.lee@lge.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox