xe_force_wake_get(9)

✨ xe_force_wake_get(9) ✨

okay so this is a page from the Kernel API Manual bestie, and it's all about xe_force_wake_get — the little function that bumps your domain refcount 💅 buckle up, it's honestly not that deep but the vibes are immaculate.

---

🌸 NAME 🌸

xe_force_wake_get — increase the domain refcount 🔥 like, that's literally it, that's the whole job.

---

🦋 SYNOPSIS 🦋

unsigned int xe_force_wake_get (struct xe_force_wake *fw , enum
       xe_force_wake_domains domains );

copy it exactly, don't freestyle the signature, i'm begging 🙈

---

🎀 ARGUMENTS 🎀

• fw — a struct xe_force_wake, the main character of this whole operation 👑
• domains — the forcewake domains you wanna get a refcount on, like picking which ones get the love 🫶

---

💖 DESCRIPTION 💖

so, what does it do? it wakes up the domains if they're asleep 😴➡️😳 and then takes references on them. that's the tea.

here's the part where you gotta pay attention though, no cap: if the requested domain is XE_FORCEWAKE_ALL, then only the applicable/initialized domains get considered for the refcount. and it is your responsibility as the caller to check the returned ref — specifically whether it includes any specific domain — by using xe_force_wake_ref_has_domain. like, the function isn't gonna hold your hand on that one 💀

also, you must call xe_force_wake_put to decrease the refcounts you just incremented. don't leave them hanging, that's rude, fr fr.

and now the big sister advice section: when possible, use scope-based forcewake instead of calling this function directly. that means going through CLASS(xe_force_wake, ...) or xe_with_force_wake. it's giving responsible adult energy ✨

so when is direct usage of get/put actually okay? two situations, and only two:

• the function has goto-based flows that can interfere with scope-based cleanup (yeah, the goto jumps really said "not today") 😭
• the lifetime of the forcewake reference doesn't match a specific scope — e.g. forcewake obtained in one function and released in a different one. different function, different vibe, it happens 🧚

---

🌈 RETURN 🌈

an opaque reference to the woken domains 🎉 or zero if none of the requested domains were awake. zero means nobody showed up to the party, don't take it personally 💀

---

⭐ SEE ALSO ⭐

• the Kernel file ./drivers/gpu/drm/xe/xe_force_wake.c — literally the source, go read it, it's iconic
• xe_force_wake_put(9) — the other half of the get/put duo, you can't have one without the other 🫶

---

okay that's the whole page bestie, you ate that 💅 and for the cute little sign-off: this legendary document comes from ./drivers/gpu/drm/xe, dated October 2026, and stars xe_force_wake_get(9) — go forth and refcount responsibly 🌸💖✨