[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251020145118.1306-1-shechenglong@xfusion.com>
Date: Mon, 20 Oct 2025 22:51:15 +0800
From: shechenglong <shechenglong@...sion.com>
To: <linux-arm-kernel@...ts.infradead.org>
CC: <mark.rutland@....com>, <catalin.marinas@....com>, <will@...nel.org>,
<linux-kernel@...r.kernel.org>, <stone.xulei@...sion.com>,
<chenjialong@...sion.com>, <yuxiating@...sion.com>
Subject: [PATCH v2 0/2] arm64: spectre: Fix hard lockup and cleanup mitigation messages
This v2 series addresses your comments:
- Fixed the message to use "command-line" consistently
- Created spectre_print_disabled_mitigations() function to handle all spectre mitigation messages
- Added a separate patch to remove the CONFIG_MITIGATE_SPECTRE_BHB option
The series includes two patches:
Patch 1: "fix hard lockup triggered by printk calls within scheduling context"
- Moves printk calls from scheduler context to setup_system_capabilities()
- Prevents hard lockups by avoiding printk in unsafe contexts
- Consolidates spectre mitigation status reporting
Patch 2: "Remove the print when the CONFIG_MITIGATE_SPECTRE_BRANCH_HISTORY Kconfig option is disabled"
- Removes the obsolete CONFIG_MITIGATE_SPECTRE_BHB Kconfig option
- Cleans up the spectre mitigation code as suggested
shechenglong (2):
arm64: spectre: fix hard lockup triggered by printk calls within scheduling context
arm64: spectre: Remove the print when the CONFIG_MITIGATE_SPECTRE_BRANCH_HISTORY Kconfig option is disabled
arch/arm64/include/asm/spectre.h | 2 ++
arch/arm64/kernel/cpufeature.c | 7 ++++++-
arch/arm64/kernel/proton-pack.c | 28 ++++++++++++++--------------
3 files changed, 22 insertions(+), 17 deletions(-)
In-Reply-To: 20250918064907.1832-1-shechenglong@...sion.com
Powered by blists - more mailing lists