On Tue, Nov 24 2020 at 20:52, Fenghua Yu wrote:
> Since #DB for bus lock detect changes the split_lock_detect parameter,
> update the documentation for the changes.
Why is this seperate and an all in one thing? patch 2/4 changes the
parameter first and 3/4 adds a new option....
>
> Signed-off-by: Fenghua Yu <fenghua...@intel.com>
> Reviewed-by: Tony Luck <tony.l...@intel.com>
> Acked-by: Randy Dunlap <rdun...@infradead.org>
> ---
> Change Log:
> 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 | 30 +++++++++++++++----
> 1 file changed, 24 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt
> b/Documentation/admin-guide/kernel-parameters.txt
> index 44fde25bb221..28228539b02a 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -5051,27 +5051,45 @@
> spia_peddr=
> +
> + ratelimit:N -
> + Set rate limit to N bus locks per second
> + for bus lock detection. 0 < N <= HZ/2.
Oh well. So if I have ratelimit:500 on the kernel command line and then
this works for CONFIG_HZ=1000, but after rebuilding the kernel with
HZ=250 it fails. What?
If I allow 500 hits per second then CONFIG_HZ has absolutely nothing to
do with it. A second stays a second independent of CONFIG_HZ.
So what's the purpose of this HZ business?
Thanks,
tglx
