mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org
Cc: "H. Peter Anvin" <hpa@zytor.com>, Tony Luck <tony.luck@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] x86/split_lock: Fix and cleanup of cpu_model_supports_sld
Date: Fri, 6 Mar 2026 10:59:53 +0800	[thread overview]
Message-ID: <9ef5afa2-18d8-4076-98ec-5571969aca31@intel.com> (raw)
In-Reply-To: <20251218080044.2615106-1-xiaoyao.li@intel.com>

On 12/18/2025 4:00 PM, Xiaoyao Li wrote:
> While considering Kiryl's suggestion[1], I'm wondering why we have
> cpu_model_supports_sld defined, which seems like it could be replaced by
> X86_FEATURE_SPLIT_LOCK_DETECT.
> 
> Tracing through the history, I find that X86_FEATURE_SPLIT_LOCK_DETECT
> originally indicated whether the kernel enabled the split lock detection
> feature, rather than enumerating hardware support for the feature, at the
> time when cpu_model_supports_sld was introduced.
> 
> Now, the semantics of X86_FEATURE_SPLIT_LOCK_DETECT have changed and
> it enuemrates the hardware support for the feature. Therefore, patch 2
> replaces cpu_model_supports_sld with X86_FEATURE_SPLIT_LOCK_DETECT.
> 
> Patch 1 fixes a potential issue where MSR_TEST_CTRL can be written when
> the split lock detection feature is not available, which can cause bizarre
> behavior.

Ping on this series.

(It applies cleanly on v7.0-rc2)

> [1] https://lore.kernel.org/all/lvobu4gpfsjg63syubgy2jwcja72folflrst7bu2eqv6rhaqre@ttbkykphu32f/
> 
> Xiaoyao Li (2):
>    x86/split_lock: Fix handling in split_lock_init()
>    x86/split_lock: Drop cpu_model_supports_sld
> 
>   arch/x86/kernel/cpu/bus_lock.c | 14 ++++----------
>   1 file changed, 4 insertions(+), 10 deletions(-)
> 


      parent reply	other threads:[~2026-03-06  2:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-18  8:00 Xiaoyao Li
2025-12-18  8:00 ` [PATCH 1/2] x86/split_lock: Fix handling in split_lock_init() Xiaoyao Li
2025-12-18  8:00 ` [PATCH 2/2] x86/split_lock: Drop cpu_model_supports_sld Xiaoyao Li
2026-03-06  2:59 ` Xiaoyao Li [this message]

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=9ef5afa2-18d8-4076-98ec-5571969aca31@intel.com \
    --to=xiaoyao.li@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --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®