__xe_drm_client_free(9)

💅 __xe_drm_client_free — the Kernel API Manual moment

okay bestie, so this one lives in the Kernel API Manual (yes, that's the manual name, we're fancy now 🎀) and it's genuinely one of those tiny-but-critical cleanup functions. no cap, it's short, but it's doing real work.

---

✨ NAME ✨

__xe_drm_client_free — free the client struct, periodt 🧹

---

🦋 SYNOPSIS 🦋

void __xe_drm_client_free (struct kref *kref );

that's it. that's the whole signature. she's small but she's main character energy 💅

---

🌸 ARGUMENTS 🌸

• kref — The reference. yes, just the reference — that's literally what the docs say, and we're not inventing lore. it's the struct kref handed to you, iykyk 🔥

---

💖 DESCRIPTION 💖

so here's the vibe check: this function frees the client struct. that's the whole thing she does, and she does it slayfully.

the docs are very clear about when you should call this API: when the xe device is closed by the drm client. that's the moment. that's your cue. don't be out here calling it whenever, bestie — the trigger is the xe device getting closed by the drm client 🙈

lowkey important: this is a free function. it's cleanup. you call it at the right moment and the client struct goes away. that's the deal, fr fr.

---

⭐ RETURN ⭐

void — she returns nothing. no value, no drama, just vibes and a freed struct 🫶

---

👑 SEE ALSO 👑

• the Kernel file ./drivers/gpu/drm/xe/xe_drm_client.c
• DRM Client usage stats(9)
• xe_drm_client_alloc(9)
• xe_drm_client_add_bo(9)
• xe_drm_client_remove_bo(9)
• xe_drm_client_fdinfo(9)

literally the whole friend group of client functions — alloc, add_bo, remove_bo, fdinfo — plus the usage stats page. go read them, they're all connected, iykyk 🌈

---

okay that's the page!! and for the cute sign-off you asked for: this one lives under ./drivers/gpu/drm/xe, dated October 2026, in the Kernel API Manual — so like, future energy but also very much today's problem. mwah, go free that client struct responsibly 😭💜 🌸