From: Thomas Gleixner <tglx@linutronix.de>
To: Fenghua Yu <fenghua.yu@intel.com>, 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: Re: [PATCH v5 3/3] Documentation/admin-guide: Change doc for split_lock_detect parameter
Date: Fri, 19 Mar 2021 22:35:46 +0100 [thread overview]
Message-ID: <87y2ei4yj1.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20210313054910.2503968-4-fenghua.yu@intel.com>
On Sat, Mar 13 2021 at 05:49, Fenghua Yu wrote:
> + ratelimit:N -
> + Set rate limit to N bus locks per second
> + for bus lock detection. 0 < N.
> + Only applied to non-root users.
Of course this does not mention that the limit is per UID and it neither
tells what the action is to rate limit the bus lock attempts. The rate
limit saturation which is induced by msleep() is not mentioned either.
Really useful for administrators.
Thanks,
tglx
prev parent reply other threads:[~2021-03-19 21:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 5:49 [PATCH v5 0/3] x86/bus_lock: Enable bus lock detection Fenghua Yu
2021-03-13 5:49 ` [PATCH v5 1/3] x86/cpufeatures: Enumerate #DB for " Fenghua Yu
2021-03-19 20:35 ` Thomas Gleixner
2021-03-19 21:00 ` Fenghua Yu
2021-03-13 5:49 ` [PATCH v5 2/3] x86/bus_lock: Handle #DB for bus lock Fenghua Yu
2021-03-19 21:30 ` Thomas Gleixner
2021-03-19 21:50 ` Luck, Tony
2021-03-20 1:01 ` Thomas Gleixner
2021-03-20 13:57 ` Thomas Gleixner
2021-04-03 0:50 ` Fenghua Yu
2021-03-19 22:19 ` Fenghua Yu
2021-03-20 12:42 ` Thomas Gleixner
2021-04-03 1:04 ` Fenghua Yu
2021-04-12 7:15 ` Thomas Gleixner
2021-04-13 23:40 ` Fenghua Yu
2021-04-14 9:41 ` Thomas Gleixner
2021-03-13 5:49 ` [PATCH v5 3/3] Documentation/admin-guide: Change doc for split_lock_detect parameter Fenghua Yu
2021-03-19 21:35 ` Thomas Gleixner [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=87y2ei4yj1.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--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=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