workqueue: Fix cpu_intensive_thresh_us name in help text
authorGeert Uytterhoeven <geert+renesas@glider.be>
Tue, 11 Jul 2023 10:38:20 +0000 (12:38 +0200)
committerTejun Heo <tj@kernel.org>
Tue, 11 Jul 2023 21:33:25 +0000 (11:33 -1000)
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 <geert+renesas@glider.be>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Tejun Heo <tj@kernel.org>
lib/Kconfig.debug

index fbc89baf7de645c12f137ba488acf16963e9f249..d6798513a8c21fe7007e34a64977a7a499d09fb4 100644 (file)
@@ -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