The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Li, Xiaoyao" <xiaoyao.li@intel.com>, Rong Zhang <i@rong.moe>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Fenghua Yu <fenghuay@nvidia.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -v2] x86/split_lock: Restructure the unwieldy switch-case in sld_state_show()
Date: Thu, 26 Feb 2026 13:01:44 -0800	[thread overview]
Message-ID: <aaC0uN04LrSemCJL@agluck-desk3> (raw)
In-Reply-To: <20260226145033.GAaaBduQ0rWXydOkAm@fat_crate.local>

On Thu, Feb 26, 2026 at 03:50:33PM +0100, Borislav Petkov wrote:

Only need the cpuhp_setup_state() for the sld_state == sld_warn case.

> +	if (boot_cpu_has(X86_FEATURE_SPLIT_LOCK_DETECT)) {
> +		pr_info("#AC: crashing the kernel on kernel split_locks and %s on user-space split_locks\n", action);
> +
	    if (sld_state == sld_warn) {
> +		/*
> +		 * This is handling the case where a CPU goes offline at the
> +		 * moment where split lock detection is disabled in the warn
> +		 * setting, see split_lock_warn(). It doesn't have any effect
> +		 * in the fatal case.
> +                 */
> +		if (cpuhp_setup_state(CPUHP_AP_ONLINE_DYN, "x86/splitlock", NULL, splitlock_cpu_offline) < 0)
> +			pr_warn("No splitlock CPU offline handler\n");
            }
> +
> +	} else if (boot_cpu_has(X86_FEATURE_BUS_LOCK_DETECT)) {
> +		pr_info("#DB: %s on user-space bus_locks\n", action);
>  	}
>  }

-Tony

  reply	other threads:[~2026-02-26 21:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 18:11 [PATCH] x86/split_lock: Remove dead kmsg formatting when split_lock_detect=fatal Rong Zhang
2026-01-04 19:17 ` [PATCH] x86/split_lock: Zap the unwieldy switch-case in sld_state_show() Borislav Petkov
2026-01-07  5:38   ` Xiaoyao Li
2026-01-07 11:28     ` Borislav Petkov
2026-01-07 16:41       ` Luck, Tony
2026-01-08 10:38         ` Borislav Petkov
2026-02-26 14:50           ` [PATCH -v2] x86/split_lock: Restructure " Borislav Petkov
2026-02-26 21:01             ` Luck, Tony [this message]
2026-02-27 16:32               ` Borislav Petkov
2026-03-06  2:57             ` Xiaoyao Li
2026-03-13 15:25               ` Borislav Petkov
2026-03-13 20:22             ` [tip: x86/cleanups] " tip-bot2 for Borislav Petkov
2026-01-04 19:18 ` [tip: x86/cleanups] x86/split_lock: Remove dead string when split_lock_detect=fatal tip-bot2 for Rong Zhang

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=aaC0uN04LrSemCJL@agluck-desk3 \
    --to=tony.luck@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=fenghuay@nvidia.com \
    --cc=hpa@zytor.com \
    --cc=i@rong.moe \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xiaoyao.li@intel.com \
    /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