From: Dave Hansen <dave.hansen@intel.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org
Cc: "H. Peter Anvin" <hpa@zytor.com>,
reinette.chatre@intel.com, Kiryl Shutsemau <kas@kernel.org>,
rick.p.edgecombe@intel.com, linux-kernel@vger.kernel.org,
chenyi.qiang@intel.com, chao.p.peng@intel.com
Subject: Re: [PATCH v2] x86/split_lock: Handle unexpected split lock as fatal
Date: Wed, 7 Jan 2026 07:19:19 -0800 [thread overview]
Message-ID: <9fbbe3bc-0912-42af-b5c0-abda89e0b621@intel.com> (raw)
In-Reply-To: <20260107134955.3293885-1-xiaoyao.li@intel.com>
On 1/7/26 05:49, Xiaoyao Li wrote:
> + /*
> + * If #AC occurs on split lock without X86_FEATURE_SPLIT_LOCK_DETECT
> + * the kernel cannot handle it by disabling the detection. Treat it as
> + * fatal regardless of the sld_state.
> + */
> + if (!cpu_feature_enabled(X86_FEATURE_SPLIT_LOCK_DETECT))
> + return true;
If #AC occurs on split lock without X86_FEATURE_SPLIT_LOCK_DETECT, that
sounds more like a naughty hypervisor or buggy CPU that deserves a
BUG_ON() rather than a situation where the kernel wants to move merrily
along.
This also needs an explanation in the changelog about _why_
X86_FEATURE_SPLIT_LOCK_DETECT isn't set and can't be set. It needs to
explain why enumeration is not present *AND* is impossible to add.
next prev parent reply other threads:[~2026-01-07 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 13:49 Xiaoyao Li
2026-01-07 15:19 ` Dave Hansen [this message]
2026-01-07 15:24 ` Edgecombe, Rick P
2026-01-07 16:06 ` Dave Hansen
2026-01-08 2:19 ` Xiaoyao Li
2026-01-08 2:11 ` Xiaoyao Li
2026-01-07 15:20 ` Kiryl Shutsemau
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=9fbbe3bc-0912-42af-b5c0-abda89e0b621@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=chao.p.peng@intel.com \
--cc=chenyi.qiang@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=rick.p.edgecombe@intel.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
all inboxes | Powered by JetHome®