mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Kaplan <david.kaplan@amd.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
	Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
	"H . Peter Anvin" <hpa@zytor.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: [PATCH v5 14/20] x86/bugs: Add attack vector controls for BHI
Date: Fri, 9 May 2025 11:28:33 -0500	[thread overview]
Message-ID: <20250509162839.3057217-15-david.kaplan@amd.com> (raw)
In-Reply-To: <20250509162839.3057217-1-david.kaplan@amd.com>

There are two BHI mitigations, one for SYSCALL and one for VMEXIT.
Split these up so they can be selected individually based on attack
vector.

Signed-off-by: David Kaplan <david.kaplan@amd.com>
---
 arch/x86/kernel/cpu/bugs.c | 38 +++++++++++++++++++++++++++-----------
 1 file changed, 27 insertions(+), 11 deletions(-)

diff --git a/arch/x86/kernel/cpu/bugs.c b/arch/x86/kernel/cpu/bugs.c
index 305a11fa9521..667385808400 100644
--- a/arch/x86/kernel/cpu/bugs.c
+++ b/arch/x86/kernel/cpu/bugs.c
@@ -1905,8 +1905,9 @@ static bool __init spec_ctrl_bhi_dis(void)
 enum bhi_mitigations {
 	BHI_MITIGATION_OFF,
 	BHI_MITIGATION_AUTO,
-	BHI_MITIGATION_ON,
+	BHI_MITIGATION_FULL,
 	BHI_MITIGATION_VMEXIT_ONLY,
+	BHI_MITIGATION_SYSCALL_ONLY
 };
 
 static enum bhi_mitigations bhi_mitigation __ro_after_init =
@@ -1920,7 +1921,7 @@ static int __init spectre_bhi_parse_cmdline(char *str)
 	if (!strcmp(str, "off"))
 		bhi_mitigation = BHI_MITIGATION_OFF;
 	else if (!strcmp(str, "on"))
-		bhi_mitigation = BHI_MITIGATION_ON;
+		bhi_mitigation = BHI_MITIGATION_FULL;
 	else if (!strcmp(str, "vmexit"))
 		bhi_mitigation = BHI_MITIGATION_VMEXIT_ONLY;
 	else
@@ -1932,11 +1933,22 @@ early_param("spectre_bhi", spectre_bhi_parse_cmdline);
 
 static void __init bhi_select_mitigation(void)
 {
-	if (!boot_cpu_has(X86_BUG_BHI) || cpu_mitigations_off())
+	if (!boot_cpu_has(X86_BUG_BHI))
 		bhi_mitigation = BHI_MITIGATION_OFF;
 
-	if (bhi_mitigation == BHI_MITIGATION_AUTO)
-		bhi_mitigation = BHI_MITIGATION_ON;
+	if (bhi_mitigation != BHI_MITIGATION_AUTO)
+		return;
+
+	if (cpu_attack_vector_mitigated(CPU_MITIGATE_USER_KERNEL)) {
+		if (cpu_attack_vector_mitigated(CPU_MITIGATE_GUEST_HOST))
+			bhi_mitigation = BHI_MITIGATION_FULL;
+		else
+			bhi_mitigation = BHI_MITIGATION_SYSCALL_ONLY;
+	} else if (cpu_attack_vector_mitigated(CPU_MITIGATE_GUEST_HOST)) {
+		bhi_mitigation = BHI_MITIGATION_VMEXIT_ONLY;
+	} else {
+		bhi_mitigation = BHI_MITIGATION_OFF;
+	}
 }
 
 static void __init bhi_update_mitigation(void)
@@ -1969,15 +1981,19 @@ static void __init bhi_apply_mitigation(void)
 	if (!IS_ENABLED(CONFIG_X86_64))
 		return;
 
-	if (bhi_mitigation == BHI_MITIGATION_VMEXIT_ONLY) {
-		pr_info("Spectre BHI mitigation: SW BHB clearing on VM exit only\n");
+	/* Mitigate KVM if guest->host protection is desired */
+	if (bhi_mitigation == BHI_MITIGATION_FULL ||
+	    bhi_mitigation == BHI_MITIGATION_VMEXIT_ONLY) {
 		setup_force_cpu_cap(X86_FEATURE_CLEAR_BHB_VMEXIT);
-		return;
+		pr_info("Spectre BHI mitigation: SW BHB clearing on VM exit\n");
 	}
 
-	pr_info("Spectre BHI mitigation: SW BHB clearing on syscall and VM exit\n");
-	setup_force_cpu_cap(X86_FEATURE_CLEAR_BHB_LOOP);
-	setup_force_cpu_cap(X86_FEATURE_CLEAR_BHB_VMEXIT);
+	/* Mitigate syscalls if user->kernel protection is desired */
+	if (bhi_mitigation == BHI_MITIGATION_FULL ||
+	    bhi_mitigation == BHI_MITIGATION_SYSCALL_ONLY) {
+		setup_force_cpu_cap(X86_FEATURE_CLEAR_BHB_LOOP);
+		pr_info("Spectre BHI mitigation: SW BHB clearing on syscall\n");
+	}
 }
 
 static void __init spectre_v2_select_mitigation(void)
-- 
2.34.1


  parent reply	other threads:[~2025-05-09 16:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09 16:28 [PATCH v5 00/20] Attack vector controls (part 2) David Kaplan
2025-05-09 16:28 ` [PATCH v5 01/20] Documentation/x86: Document new attack vector controls David Kaplan
2025-05-09 16:28 ` [PATCH v5 02/20] cpu: Define attack vectors David Kaplan
2025-05-21 15:28   ` Borislav Petkov
2025-05-09 16:28 ` [PATCH v5 03/20] x86/Kconfig: Add arch attack vector support David Kaplan
2025-05-09 16:28 ` [PATCH v5 04/20] x86/bugs: Define attack vectors relevant for each bug David Kaplan
2025-05-09 16:28 ` [PATCH v5 05/20] x86/bugs: Add attack vector controls for MDS David Kaplan
2025-05-09 16:28 ` [PATCH v5 06/20] x86/bugs: Add attack vector controls for TAA David Kaplan
2025-05-09 16:28 ` [PATCH v5 07/20] x86/bugs: Add attack vector controls for MMIO David Kaplan
2025-05-09 16:28 ` [PATCH v5 08/20] x86/bugs: Add attack vector controls for RFDS David Kaplan
2025-05-09 16:28 ` [PATCH v5 09/20] x86/bugs: Add attack vector controls for SRBDS David Kaplan
2025-05-09 16:28 ` [PATCH v5 10/20] x86/bugs: Add attack vector controls for GDS David Kaplan
2025-05-09 16:28 ` [PATCH v5 11/20] x86/bugs: Add attack vector controls for spectre_v1 David Kaplan
2025-05-09 16:28 ` [PATCH v5 12/20] x86/bugs: Add attack vector controls for retbleed David Kaplan
2025-05-09 16:28 ` [PATCH v5 13/20] x86/bugs: Add attack vector controls for spectre_v2_user David Kaplan
2025-05-09 16:28 ` David Kaplan [this message]
2025-06-30 12:40   ` [PATCH v5 14/20] x86/bugs: Add attack vector controls for BHI Borislav Petkov
2025-07-01  3:27     ` Kaplan, David
2025-07-01 11:45       ` Borislav Petkov
2025-07-02 18:24         ` Kaplan, David
2025-07-03 10:01           ` Borislav Petkov
2025-05-09 16:28 ` [PATCH v5 15/20] x86/bugs: Add attack vector controls for spectre_v2 David Kaplan
2025-05-09 16:28 ` [PATCH v5 16/20] x86/bugs: Add attack vector controls for L1TF David Kaplan
2025-05-09 16:28 ` [PATCH v5 17/20] x86/bugs: Add attack vector controls for SRSO David Kaplan
2025-05-09 16:28 ` [PATCH v5 18/20] x86/pti: Add attack vector controls for PTI David Kaplan
2025-05-09 16:28 ` [PATCH v5 19/20] x86/bugs: Print enabled attack vectors David Kaplan
2025-05-09 16:28 ` [PATCH v5 20/20] cpu: Show attack vectors in sysfs David Kaplan
2025-06-30 16:40 ` [PATCH v5 00/20] Attack vector controls (part 2) Borislav Petkov
2025-07-01  3:27   ` Kaplan, David

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=20250509162839.3057217-15-david.kaplan@amd.com \
    --to=david.kaplan@amd.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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

all inboxes | Powered by JetHome®