UAPI TRACE EVENTS(9)

💅 uAPI trace events 💅

okay so welcome to the Kernel API Manual page for uAPI trace events(9) 💖 bestie, this one is short but iconic.

The stable uAPI crew is drm_sched_job_queue, drm_sched_job_run, drm_sched_job_add_dep, drm_sched_job_done, and drm_sched_job_unschedulable — these are considered stable uAPI, periodt. 👑

Common trace events attributes:

• dev — the dev_name of the device running the job.
• ring — the hardware ring running the job. Together with dev, it uniquely identifies where the job is going to be executed. 📍
• fence — the struct dma_fence.context and the struct dma_fence.seqno of struct drm_sched_fence.finished.

All the events depend on drm_sched_job_arm having been called already for the job, because they use struct drm_sched_job.sched or struct drm_sched_job.s_fence. lowkey crucial info, no cap. ✨

🦋 SEE ALSO 🦋

• Kernel file: ./drivers/gpu/drm/scheduler/gpu_scheduler_trace.h

okay byeee bestie 💋 the source/version is ./drivers/gpu/drm/scheduler, the date is October 2026, and this is literally the uAPI trace events(9) page — mwah 🫶 slay 💖