drm_sched_jo...j_dependency(9)

📦 version 7.3.1, in nixpkgs unstable

💜 drm_sched_jo...j_dependency(9) — straight from the Kernel API Manual, bestie

okay so picture this: you're deep in the kernel, the manual name is Kernel API Manual, and we're about to talk about one very specific little function that quietly does a LOT of heavy lifting. pull up a chair 🎀

✨ NAME ✨

drm_sched_job_add_syncobj_dependency — adds a syncobj's fence as a job dependency. that's it, that's the whole vibe 💅

🦋 SYNOPSIS 🦋

int drm_sched_job_add_syncobj_dependency (struct drm_sched_job *job ,
       struct drm_file *file , u32 handle , u32 point );

like, four args, one int back. slay, honestly ✨

🌸 ARGUMENTS 🌸

  • job — the scheduler job you're adding dependencies to. it's the main character here 👑
  • file — the drm file private pointer, aka the DRM-side context you're rolling with
  • handle — the syncobj handle you wanna look up, iykyk
  • point — the timeline point. yes, that timeline point 💫

🧚 DESCRIPTION 🧚

so what does it actually do? it takes the fence that matches the syncobj you gave it and adds it to job. that's the whole tea, no cap. fence in → dependency attached → job knows what it's waiting on 🫶

🌈 RETURN 🌈

  • 0 on success 🎉
  • or an error on failing to expand the array 😭 (the array run out of room, it happens to the best of us)

⭐ SEE ALSO ⭐

okay this list is LONG and honestly iconic, buckle up bestie:

like, the whole sched family reunion fr fr 🫶

💀 reminder bestie: error only happens when the array can't expand. don't @ me, that's literally what the page says.

and that's the page!! brought to you by ./drivers/gpu/drm/scheduler, dated October 2026, page name drm_sched_jo...j_dependency(9). go forth and add those dependencies, queen 👑💖

📦 where this page comes from