dma_resv_for_each_fence(9)

✨ NAME ✨

dma_resv_for_each_fence — fence iterator. this is the Kernel API Manual page for dma_resv_for_each_fence(9), and bestie, it’s giving “lock held, fences handled” energy 💅

🌸 SYNOPSIS 🌸

dma_resv_for_each_fence (cursor , obj , usage , fence );

🎀 ARGUMENTS 🎀

• cursor — a struct dma_resv_iter pointer.
• obj — a dma_resv object pointer.
• usage — controls which fences to return.
• fence — the current fence.

🦋 DESCRIPTION 🦋

okay so here’s the vibe: you iterate over the fences in a struct dma_resv object while holding the dma_resv.lock. all_fences controls if the shared fences are returned as well. the cursor initialisation is part of the iterator, and the fence stays valid as long as the lock is held — so no extra reference to the fence is taken. periodt 💅

🌈 SEE ALSO 🌈

• Kernel file ./include/linux/dma-resv.h — enum dma_resv_usage(9)
• dma_resv_usage_rw(9)
• struct dma_resv(9)
• struct dma_resv_iter(9)
• dma_resv_iter_begin(9)
• dma_resv_iter_end(9)
• dma_resv_iter_usage(9)
• dma_resv_iter_is_restarted(9)
• dma_resv_for_each_fence_unlocked(9)
• dma_resv_lock(9)
• dma_resv_lock_interruptible(9)
• dma_resv_lock_slow(9)
• dma_resv_lock_slow_interruptible(9)
• dma_resv_trylock(9)
• dma_resv_is_locked(9)
• dma_resv_locking_ctx(9)
• dma_resv_unlock(9)

mwah 💋 this page comes from ./include/linux and is dated October 2026 — Kernel API Manual representation, iykyk. bye bestie, go hold that lock and slay 🫶