dma_resv_get_singleton(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dma_resv_get_singleton — the dma_resv_get_singleton(9) page, bestie edition

okay so real talk, this is a kernel API manual page, and it's literally about getting one fence to rule them all ✨

🎀 NAME 🎀

dma_resv_get_singleton — Get a single fence for all the fences. that's it, that's the whole vibe 🫶

⭐ SYNOPSIS ⭐

int dma_resv_get_singleton (struct dma_resv *obj , enum dma_resv_usage
usage , struct dma_fence **fence );

not me putting the whole signature in a code block so nothing gets mistyped 💀 keep it exactly like that, every pointer and comma, fr fr.

🌸 ARGUMENTS 🌸

  • obj — the reservation object. your main character struct 👑
  • usage — controls which fences to include, see enum dma_resv_usage. so like, it's the vibe check for which fences get invited to the party 🎉
  • fence — the resulting fence. the one (1) fence that comes out the other side 🦋

✨ DESCRIPTION ✨

So what does it actually do? It gets a single fence representing all the fences inside the resv object. like a group photo but make it a fence 📸

Returns either 0 for success or -ENOMEM. that's the whole return menu, no hidden items 😭

⚠️ Warning: This can't be used like this when adding the fence back to the resv object, since that can lead to stack corruption when finalizing the dma_fence_array. like, seriously, do NOT do that. this is the "danger, do not touch" part of the page, and I'm not being dramatic, it's literally in the manual 💀🔥

Returns 0 on success and negative error values on failure. yes, it says the success/failure thing twice, and yes, I'm keeping both because you don't skip details in this house 🙈

👑 SEE ALSO 👑

every single one of them, in the exact order, because that's the whole squad 🫶✨

okay that's the page!! mwah 💖 this icon came from ./drivers/dma-buf, dated October 2026, and it's filed under dma_resv_get_singleton(9) — slay, go read a fence, ily, bye 🎀🌈💜

📦 where this page comes from