xe_sync_ufence_get_status(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_sync_ufence_get_status πŸ’…

okay so bestie, welcome to the Kernel API Manual entry for xe_sync_ufence_get_status β€” yes that's a whole mouthful, i know, but it's lowkey iconic and we're gonna get through it together 🫢


✨ NAME ✨

xe_sync_ufence_get_status β€” gets the status of a user fence. that's it. that's the vibe. user fence status getter, main character energy, no cap πŸ’…


🌸 SYNOPSIS 🌸

int xe_sync_ufence_get_status (struct xe_user_fence *ufence );

that's the whole signature, she's short and she knows it ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • ufence β€” the user fence. like, the actual struct xe_user_fence * you're asking about. that's the one. that's her πŸ‘‘

πŸ¦‹ RETURN πŸ¦‹

the return value is doing a little three-way vibe check, so pay attention bestie:

  • 1 β€” signalled πŸ’– (yay, it happened!)
  • 0 β€” not signalled πŸ™ˆ (not yet, be patient)
  • <0 β€” error πŸ’€ (something went wrong, go check)
fr fr remember: 1 means yes, 0 means no, and anything below 0 means it's giving error energy. don't mix them up 😭

πŸ”₯ SEE ALSO πŸ”₯

the whole friend group, all linked from the kernel file ./drivers/gpu/drm/xe/xe_sync.c:

go read those too, iykyk 🧚


and that's the page!! mwah πŸ’‹ this whole thing lives in ./drivers/gpu/drm/xe, dated October 2026 β€” so when you cite it, cite it cute. slay, periodt, bye bestie πŸŽ€βœ¨

πŸ“¦ where this page comes from