From: Fenghua Yu <fenghua.yu@intel.com>
To: "Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"Peter Zijlstra" <peterz@infradead.org>,
"Tony Luck" <tony.luck@intel.com>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Xiaoyao Li " <xiaoyao.li@intel.com>,
"Ravi V Shankar" <ravi.v.shankar@intel.com>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>,
"x86" <x86@kernel.org>, Fenghua Yu <fenghua.yu@intel.com>
Subject: [PATCH v6 3/3] Documentation/admin-guide: Change doc for split_lock_detect parameter
Date: Mon, 22 Mar 2021 13:53:25 +0000 [thread overview]
Message-ID: <20210322135325.682257-4-fenghua.yu@intel.com> (raw)
In-Reply-To: <20210322135325.682257-1-fenghua.yu@intel.com>
Since #DB for bus lock detect changes the split_lock_detect parameter,
update the documentation for the changes.
Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
Reviewed-by: Tony Luck <tony.luck@intel.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
---
Change Log:
v6:
- Remove the ratelimit info which will be released later in a ratelimit
specific patch set (Thomas).
v5:
- Remove N < HZ/2 check info in the doc (Thomas).
v4:
- Fix a ratelimit wording issue in the doc (Randy).
- Patch 4 is acked by Randy (Randy).
v3:
- Enable Bus Lock Detection when fatal to handle bus lock from non-WB
(PeterZ).
v1:
- Fix a few wording issues (Randy).
RFC v2:
- Simplify the documentation (Randy).
.../admin-guide/kernel-parameters.txt | 22 ++++++++++++++-----
1 file changed, 16 insertions(+), 6 deletions(-)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index 04545725f187..aef927cec602 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -5100,27 +5100,37 @@
spia_peddr=
split_lock_detect=
- [X86] Enable split lock detection
+ [X86] Enable split lock detection or bus lock detection
When enabled (and if hardware support is present), atomic
instructions that access data across cache line
- boundaries will result in an alignment check exception.
+ boundaries will result in an alignment check exception
+ for split lock detection or a debug exception for
+ bus lock detection.
off - not enabled
- warn - the kernel will emit rate limited warnings
+ warn - the kernel will emit rate-limited warnings
about applications triggering the #AC
- exception. This mode is the default on CPUs
- that supports split lock detection.
+ exception or the #DB exception. This mode is
+ the default on CPUs that support split lock
+ detection or bus lock detection. Default
+ behavior is by #AC if both features are
+ enabled in hardware.
fatal - the kernel will send SIGBUS to applications
- that trigger the #AC exception.
+ that trigger the #AC exception or the #DB
+ exception. Default behavior is by #AC if
+ both features are enabled in hardware.
If an #AC exception is hit in the kernel or in
firmware (i.e. not while executing in user mode)
the kernel will oops in either "warn" or "fatal"
mode.
+ #DB exception for bus lock is triggered only when
+ CPL > 0.
+
srbds= [X86,INTEL]
Control the Special Register Buffer Data Sampling
(SRBDS) mitigation.
--
2.31.0
next prev parent reply other threads:[~2021-03-22 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 13:53 [PATCH v6 0/3] x86/bus_lock: Enable bus lock detection Fenghua Yu
2021-03-22 13:53 ` [PATCH v6 1/3] x86/cpufeatures: Enumerate #DB for " Fenghua Yu
2021-03-28 21:32 ` [tip: x86/splitlock] " tip-bot2 for Fenghua Yu
2021-03-22 13:53 ` [PATCH v6 2/3] x86/bus_lock: Handle #DB for bus lock Fenghua Yu
2021-03-28 21:32 ` [tip: x86/splitlock] x86/traps: " tip-bot2 for Fenghua Yu
2021-03-22 13:53 ` Fenghua Yu [this message]
2021-03-28 21:32 ` [tip: x86/splitlock] Documentation/admin-guide: Change doc for split_lock_detect parameter tip-bot2 for Fenghua Yu
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=20210322135325.682257-4-fenghua.yu@intel.com \
--to=fenghua.yu@intel.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@intel.com \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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®