On 2/18/24 23:46, Xuewen Yan wrote: > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt > index 31b3a25680d0..599fc59fcf70 100644 > --- a/Documentation/admin-guide/kernel-parameters.txt > +++ b/Documentation/admin-guide/kernel-parameters.txt > @@ -7225,6 +7225,15 @@ > threshold repeatedly. They are likely good > candidates for using WQ_UNBOUND workqueues instead. > > + workqueue.cpu_intensive_warning_per_count= workqueue.cpu_intensive_warning_per_count=<uint> or <integer> > + If CONFIG_WQ_CPU_INTENSIVE_REPORT is set, the kernel > + will report the work functions which violate the > + intensive_threshold_us repeatedly. In order to prevent > + the kernel log from being printed too frequently. frequently, control > + Control the frequency. > + > + Default, it will print one warning per 4 times. By default, > + -- #Randy
