drm_sched_j...dependencies(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_sched_job_add_implicit_dependencies(9) β€” like, the Kernel API Manual girlies finally got one πŸŽ€

okay so bestie, welcome to the Kernel API Manual entry for drm_sched_j...dependencies(9) β€” yes the header is abbreviated, no I don't know why, and yes we're gonna get through this together. grab a strawberry drink πŸ“ and let's go.


✨ NAME ✨

drm_sched_job_add_implicit_dependencies β€” adds implicit dependencies as job dependencies 🫢


🌸 SYNOPSIS 🌸

int drm_sched_job_add_implicit_dependencies (struct drm_sched_job *job ,
struct drm_gem_object *obj , bool write );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • job β€” the scheduler job you're adding the dependencies to. main character energy, it's receiving the deps πŸ’–
  • obj β€” the gem object you're adding new dependencies from.
  • write β€” whether the job might write the object. and if it might? then we need to depend on shared fences in the reservation object. no cap, that's the whole bit πŸ”₯

πŸ’œ DESCRIPTION πŸ’œ

This should be called after drm_gem_lock_reservations on your array of GEM objects used in the job, but before updating the reservations with your own fences.

like β€” order matters, bestie. before. not after. the way that sequencing is literally the entire vibe check 😭✨


⭐ RETURN ⭐

0 on success, or an error on failing to expand the array. that's it, that's the return πŸ’€


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/gpu/drm/scheduler/sched_main.c β€” plus the whole friend group, honestly:

like that's a whole squad and every single one of them is invited πŸ§šπŸ’…


ok that's the page!! it lives in ./drivers/gpu/drm/scheduler, it's dated October 2026, and the footer spells it drm_sched_j...dependencies(9) β€” abbreviated again, iconic behaviour honestly. go add those implicit deps, bestie, you're gonna slay πŸŒˆβœ¨πŸ’–
πŸ“¦ where this page comes from