diff options
| author | Xuewen Yan <xuewen.yan@unisoc.com> | 2024-02-22 15:28:08 +0800 |
|---|---|---|
| committer | Tejun Heo <tj@kernel.org> | 2024-02-22 07:50:45 -1000 |
| commit | ccdec92198df0c91f45a68f971771b6b0c1ba02d (patch) | |
| tree | 3b59c5572a4ce81a76168b922480cd45b201f89e /tools/testing | |
| parent | workqueue: Make @flags handling consistent across set_work_data() and friends (diff) | |
| download | linux-ccdec92198df0c91f45a68f971771b6b0c1ba02d.tar.gz linux-ccdec92198df0c91f45a68f971771b6b0c1ba02d.zip | |
workqueue: Control intensive warning threshold through cmdline
When CONFIG_WQ_CPU_INTENSIVE_REPORT is set, the kernel will report
the work functions which violate the intensive_threshold_us repeatedly.
And now, only when the violate times exceed 4 and is a power of 2,
the kernel warning could be triggered.
However, sometimes, even if a long work execution time occurs only once,
it may cause other work to be delayed for a long time. This may also
cause some problems sometimes.
In order to freely control the threshold of warninging, a boot argument
is added so that the user can control the warning threshold to be printed.
At the same time, keep the exponential backoff to prevent reporting too much.
By default, the warning threshold is 4.
tj: Updated kernel-parameters.txt description.
Signed-off-by: Xuewen Yan <xuewen.yan@unisoc.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'tools/testing')
0 files changed, 0 insertions, 0 deletions