diff options
| author | Geert Uytterhoeven <[email protected]> | 2023-07-11 12:38:20 +0200 |
|---|---|---|
| committer | Tejun Heo <[email protected]> | 2023-07-11 11:33:25 -1000 |
| commit | b2ec116aad38aa9c8b67fad4314e50823adf6949 (patch) | |
| tree | c9257b650dd74bbae8dc098b79aee890446bacb9 | |
| parent | 3f01e9fed8454dcd89727016c3e5b2fbb8f8e50c (diff) | |
workqueue: Fix cpu_intensive_thresh_us name in help text
There exists no parameter called "cpu_intensive_threshold_us".
The actual parameter name is "cpu_intensive_thresh_us".
Fixes: 6363845005202148 ("workqueue: Report work funcs that trigger automatic CPU_INTENSIVE mechanism")
Signed-off-by: Geert Uytterhoeven <[email protected]>
Reviewed-by: Randy Dunlap <[email protected]>
Signed-off-by: Tejun Heo <[email protected]>
| -rw-r--r-- | lib/Kconfig.debug | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug index fbc89baf7de6..d6798513a8c2 100644 --- a/lib/Kconfig.debug +++ b/lib/Kconfig.debug @@ -1200,7 +1200,7 @@ config WQ_CPU_INTENSIVE_REPORT help Say Y here to enable reporting of concurrency-managed per-cpu work items that hog CPUs for longer than - workqueue.cpu_intensive_threshold_us. Workqueue automatically + workqueue.cpu_intensive_thresh_us. Workqueue automatically detects and excludes them from concurrency management to prevent them from stalling other per-cpu work items. Occassional triggering may not necessarily indicate a problem. Repeated |