diff options
| author | Aaron Tomlin <atomlin@atomlin.com> | 2026-09-04 15:34:45 -0400 |
|---|---|---|
| committer | Tejun Heo <tj@kernel.org> | 2026-09-04 10:20:22 -1000 |
| commit | a4d1cdc4356de4325b0a9c6fb09afa6e121407b5 (patch) | |
| tree | 35493c13aa738ed44b5255ee618df67a2da4046c /scripts/Makefile.thinlto | |
| parent | ab85b68e630e8a4db0271165149589d7702c2532 (diff) | |
| download | linux-next-a4d1cdc4356de4325b0a9c6fb09afa6e121407b5.tar.gz linux-next-a4d1cdc4356de4325b0a9c6fb09afa6e121407b5.zip | |
workqueue: Add workqueue_cpu_intensive tracepoint
When a concurrency-managed per-CPU work item runs continuously without
sleeping for longer than wq_cpu_intensive_thresh_us, wq_worker_tick() marks
the worker as WORKER_CPU_INTENSIVE and kicks it out of concurrency
management so that pending work items on the pool are not starved.
While CONFIG_WQ_CPU_INTENSIVE_REPORT logs rate-limited warnings and
pwq->stats[PWQ_STAT_CPU_INTENSIVE] maintains a cumulative counter, there is
currently no tracepoint emitted at the moment of this transition.
Therefore, add the workqueue_cpu_intensive tracepoint, recording the
work_struct pointer and callback function pointer, workqueue name,
executing CPU, and the runtime duration consumed in microseconds.
This enables eBPF profilers, bpftrace, and Ftrace to immediately detect and
attribute CPU-hogging work items in real time.
Signed-off-by: Aaron Tomlin <atomlin@atomlin.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
