drm_exec_ret...n_contention(9)

💅 drm_exec_retry_on_contention ✨

okay so real talk, the header on this one gets chopped in the terminal (drm_exec_ret...n_contention(9), tragic 😭) but it's from the Kernel API Manual and it is exactly what it sounds like: the little control-flow helper that says "bestie, we hit contention, wrap it up and run it back." 🌀

---

🌸 NAME 🌸

drm_exec_retry_on_contention — restart the loop so we can grab all the locks 🫶

---

✨ SYNOPSIS ✨

drm_exec_retry_on_contention (exec );

---

🎀 ARGUMENTS 🎀

• exec — the drm_exec object. that's the whole vibe check, one (1) argument, no notes 💅

---

🦋 DESCRIPTION 🦋

So this is a control flow helper 👑 — its whole job is to keep things moving when a contention was detected and we need to clean up and re-start the loop to prepare all the GEM objects. like, everyone out of the pool, we're resetting 🔥

⚠️ okay important: there's a __drm_exec_loop check in here, and it exists specifically to prevent usage outside of a drm_exec_until_all_locked loop. so do not be out here calling it wherever, the check will catch you and it will not be cute 🙈

---

🌈 SEE ALSO 🌈

Kernel file ./include/drm/drm_exec.h — plus the whole friend group:

• struct drm_exec(9)
• drm_exec_obj(9)
• drm_exec_for_each_locked_object(9)
• drm_exec_for_each_locked_object_reverse(9)
• drm_exec_until_all_locked(9)
• drm_exec_is_contended(9)
• drm_exec_retry(9)
• drm_exec_ticket(9)

---

and that's the page, periodt 💜 this one lives in ./include/drm, it's the October 2026 drop, and it's part of the Kernel API Manual — go read drm_exec_until_all_locked(9) next, iykyk 🧚‍♀️✨