dma_fence_get_status_locked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

okay so bestie, this is dma_fence_get_status_locked(9) from the Kernel API Manual, and its whole personality is: dma_fence_get_status_locked β€” returns the status upon completion. that's it, that's the name, and it's lowkey iconic ✨

πŸ“œ SYNOPSIS πŸ“œ

int dma_fence_get_status_locked (struct dma_fence *fence );

🧡 ARGUMENTS 🧡

  • fence β€” the dma_fence to query. literally the one thing you're asking about, no cap πŸ”

πŸ’– DESCRIPTION πŸ’–

okay so here's the tea, bestie. Drivers can supply an optional error status condition before they signal the fence (to indicate whether the fence was completed due to an error rather than success). The value of the status condition is only valid if the fence has been signaled, so dma_fence_get_status_locked first checks the signal state before reporting the error status. periodt πŸ’…

Important vibe check: that status condition's value is only valid if the fence has been signaled β€” do not skip that part, bestie 😭

It returns 0 if the fence has not yet been signaled, 1 if the fence has been signaled without an error condition, or a negative error code if the fence has been completed in err. the way that's so clear and organized, we love to see it 🫢

πŸ‘€ SEE ALSO πŸ‘€

Kernel file ./include/linux/dma-fence.h is the home base 🏠 and here's the full squad, no one left behind:


mwah πŸ’‹ this lil page lives under ./include/linux, is dated October 2026, and answers to dma_fence_get_status_locked(9). catch u later, bestie πŸ«ΆπŸ’œ

πŸ“¦ where this page comes from