dma_fence_work_commit_imm(9)

✨ dma_fence_work_commit_imm(9) ✨

okay bestie, welcome to the Kernel API Manual 💖 this one is short but it's giving “tiny function, very specific rules,” and honestly? iconic.

---

🌸 NAME 🌸

dma_fence_work_commit_imm — commit the fence, and if possible execute locally. slay.

---

🎀 SYNOPSIS 🎀

void dma_fence_work_commit_imm (struct dma_fence_work *f );

---

🦋 ARGUMENTS 🦋

• f — the fenced worker. that's the whole vibe 🫶

---

💅 DESCRIPTION 💅

So instead of always scheduling a worker to execute the callback (see dma_fence_work_commit), this function tries to execute the callback immediately in the local context. no cap, that's the whole point.

⚠️ but listen: it is required that the fence be committed before it is published, and that no other threads try to tamper with the number of asynchronous waits on the fence. if they do? the callback will be executed in the wrong context — i.e. not the callers. and that's not cute at all 😭

like, this is not a “maybe try it and see” situation. it's a “respect the rules or the context gets messy” situation. periodt.

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/i915/i915_sw_fence_work.h 👑

---

mwah 💋 this little page came from ./drivers/gpu/drm/i915, dated October 2026 — stay fenced, stay local, and don't let the wrong context catch you lacking 🧚✨