drm_exec_fo...ocked_object(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_exec_fo...ocked_object(9) β€” from the Kernel API Manual, bestie

okay so picture this: it's a kernel API manual page, it's October 2026 in ./include/drm, and we're about to learn a macro together. stay with me, it's gonna slay πŸŽ€

✨ NAME ✨

drm_exec_for_each_locked_object β€” literally just iterate over all the locked objects. that's the whole vibe. πŸ‘‘

🌸 SYNOPSIS 🌸

drm_exec_for_each_locked_object (exec , obj );

yes the spacing is like that, don't come for me, I don't make the rules πŸ’…

πŸ¦‹ ARGUMENTS πŸ¦‹

  • exec β€” the drm_exec object. your container, your main character, the whole reason we're here 🫢
  • obj β€” the current GEM object. this is the one you get handed on every loop trip around the sun ✨

πŸ’– DESCRIPTION πŸ’–

okay so here's the tea: this bad boy iterates over all the explicitly locked GEM objects inside the drm_exec container. all of them. every single one. no cap. πŸ”₯

but! and this is the important part β€” it skips the contended one and it skips the implicit prelocked one. those two are NOT invited to this party πŸ™ˆ not on the list, not getting in, the bouncer knows their faces.

so like, explicitly locked = yes bestie, contended and implicit prelocked = not today. got it? iconic. periodt. πŸ’€

⭐ SEE ALSO ⭐


and that's the page!! πŸ“ go forth and iterate responsibly. this lil love letter came to you straight from ./include/drm and it's dated October 2026 β€” remember us fondly, mwah πŸ’œπŸ¦‹βœ¨

πŸ“¦ where this page comes from