summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorAaron Tomlin <atomlin@atomlin.com>2026-09-04 15:34:46 -0400
committerTejun Heo <tj@kernel.org>2026-09-04 10:20:56 -1000
commita53b50e21af2eb8d4e74c8f84e409692a3332588 (patch)
treee54284332419793cb0101561fe6eabb81951fc11 /scripts/Makefile.thinlto
parenta4d1cdc4356de4325b0a9c6fb09afa6e121407b5 (diff)
downloadlinux-next-a53b50e21af2eb8d4e74c8f84e409692a3332588.tar.gz
linux-next-a53b50e21af2eb8d4e74c8f84e409692a3332588.zip
workqueue: Add workqueue_mayday and workqueue_rescued tracepoints
When a worker pool fails to create a new worker thread (e.g., typically under severe memory pressure where memory reclaim paths depend on pending work items), send_mayday() signals distress to the workqueue's rescuer thread. The rescuer then takes over processing the pending work items via assign_rescuer_work(). While pwq->stats[PWQ_STAT_MAYDAY] and pwq->stats[PWQ_STAT_RESCUED] track these occurrences cumulatively, there is currently no event-driven mechanism to observe exactly when mayday distress occurs or which work items require rescue. Add two new tracepoints namely workqueue_mayday and workqueue_rescued to make distress and rescuer execution easily observable (e.g., via Ftrace or eBPF). 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