__xe_sync_ufence_get(9)

📦 version 7.3.1, in nixpkgs unstable

💅 __xe_sync_ufence_get (9) — from the Kernel API Manual, bestie 🎀

Okay so picture this: you're deep in drivers/gpu/drm/xe land, it's giving kernel API, it's giving graphics driver, and you need a user fence reference. That's literally what this function is for. Let's get into it ✨

🌸 NAME 🌸

__xe_sync_ufence_get — get a user fence from a user fence 🦋

Like, yes, that's the whole bit: it's the getter. For the user fence. From the user fence. Iconic circular-sounding phrasing, no cap, but that's genuinely what the manpage says and we're not gonna argue with kernel docs 💀

✨ SYNOPSIS ✨

struct xe_user_fence * __xe_sync_ufence_get (struct xe_user_fence
*ufence );

That's the whole signature — it takes one struct xe_user_fence * and hands you back another struct xe_user_fence *. Simple. Clean. Main character energy 👑

🧚 ARGUMENTS 🧚

  • ufence — the input user fence 🫶 that's it, that's the argument, it's the fence you're feeding in

💖 DESCRIPTION 💖

Get a user fence reference from user fence.

That's the official line and honestly? It ate. Short, sweet, does exactly what it says on the tin. You pass in a user fence, you get a reference to it. No drama, no extra lore, no secret side quests 🌈

⭐ RETURN ⭐

A xe_user_fence pointer, with a reference 💅 — so like, you're walking away holding a ref, and you should probably remember you're holding it (xe_sync_ufence_put(9) is literally right there in SEE ALSO, just saying 🙈).

🔥 SEE ALSO 🔥

Go read these, bestie, iykyk:

Heads up 🌸 this page is the double-underscore version (__xe_sync_ufence_get), and the SEE ALSO list also has the single-underscore xe_sync_ufence_get(9). They're two different entries in the docs — don't get it twisted, keep both 💜

And that's the whole page! Source/version vibes: this one lives under ./drivers/gpu/drm/xe, dated October 2026, and it's page __xe_sync_ufence_get(9) of the Kernel API Manual. Slay, go get your fence references responsibly 🎀💖✨

📦 where this page comes from