From: Fenghua Yu <fenghua.yu@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Tony Luck <tony.luck@intel.com>,
Christopherson Sean J <sean.j.christopherson@intel.com>,
Ashok Raj <ashok.raj@intel.com>,
Ravi V Shankar <ravi.v.shankar@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH RFC v3 4/4] Documentation/admin-guide: Change doc for split_lock_detect parameter
Date: Mon, 2 Nov 2020 17:03:18 +0000 [thread overview]
Message-ID: <20201102170318.GA3666727@otcwcpicx6.sc.intel.com> (raw)
In-Reply-To: <ed101622-11f8-0b98-76ad-6c100a2574da@infradead.org>
Hi, Randy,
On Fri, Oct 30, 2020 at 08:14:15PM -0700, Randy Dunlap wrote:
> On 10/30/20 5:27 PM, Fenghua Yu wrote:
> > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> > index 526d65d8573a..ee419ce659f5 100644
> > --- a/Documentation/admin-guide/kernel-parameters.txt
> > +++ b/Documentation/admin-guide/kernel-parameters.txt
> > @@ -5044,27 +5044,45 @@
> > 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
>
> rate-limited
>
> > 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 supports split lock
>
> support
>
> > + detection or bus lock detection. Default
> > + behavior is from #DB if both features are
>
> I would say is by #DB
>
> > + 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 from #AC
>
> and is by #AC
>
> > + if both features are enabled in hardware.
> > +
> > + ratelimit:N -
> > + Set rate limit to N bus locks per second
> > + for bus lock detection. 0 < N <= HZ/2 and
> > + N is approximate. Only applied to non root
>
> non-root
>
> > + user.
>
> users.
I'll fix the issues in the next version.
Thank you very much for your review!
-Fenghua
prev parent reply other threads:[~2020-11-02 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 0:27 [PATCH RFC v3 0/4] x86/bus_lock: Enable bus lock detection Fenghua Yu
2020-10-31 0:27 ` [PATCH RFC v3 1/4] x86/cpufeatures: Enumerate #DB for " Fenghua Yu
2020-10-31 0:27 ` [PATCH RFC v3 2/4] x86/bus_lock: Handle warn and fatal in #DB for bus lock Fenghua Yu
2020-11-03 12:15 ` Xiaoyao Li
2020-11-06 20:31 ` Fenghua Yu
2020-10-31 0:27 ` [PATCH RFC v3 3/4] x86/bus_lock: Set rate limit " Fenghua Yu
2020-10-31 0:27 ` [PATCH RFC v3 4/4] Documentation/admin-guide: Change doc for split_lock_detect parameter Fenghua Yu
2020-10-31 3:14 ` Randy Dunlap
2020-11-02 17:03 ` Fenghua Yu [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=20201102170318.GA3666727@otcwcpicx6.sc.intel.com \
--to=fenghua.yu@intel.com \
--cc=ashok.raj@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=sean.j.christopherson@intel.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®