i915_request_active_engine(9)

💅 i915_request_active_engine — kernel API manual ✨

okay so bestie, welcome to i915_request_active_engine, straight out of the Kernel API Manual 📖 — yes it's a real manual page, yes it's about i915 requests, and yes we're gonna get through it together 🫶

---

🌸 NAME 🌸

i915_request_active_engine — the little helper that tells you which engine a request is currently vibing on 👑

(the original leaves the description blank, so like… that's the whole name section, no cap 💀)

---

✨ SYNOPSIS ✨

bool i915_request_active_engine (struct i915_request *rq , struct
intel_engine_cs **active );

that's it, that's the whole signature 🎀 returns a bool, takes two pointers, iconic behavior honestly

---

🦋 ARGUMENTS 🦋

• rq — the request you want to inspect 🔍 like, the main character of this whole operation
• active — a pointer where the active engine gets returned 🎯 yes it's a struct intel_engine_cs **, double pointer, she's fancy like that 💅

---

💖 DESCRIPTION 💖

so here's the tea ☕ — this function fills the currently active engine into the active pointer if the request is active and still not completed. like, if it's done, no engine for you bestie 🙈

it returns true if the request was active, or false otherwise. simple, clean, slay 🌟

ngl, that's the entire description — no hidden lore, no extra caveats, the manpage is short and she knows it 😭

---

🔥 SEE ALSO 🔥

peep the kernel file if you wanna read the source, she's right here:

• ./drivers/gpu/drm/i915/i915_request.c

and the whole friend group 💜:

• i915_request_free_capture_list(9)
• i915_request_await_deps(9)
• i915_request_await_object(9)
• i915_request_wait_timeout(9)
• i915_request_wait(9)

---

🫶 and that's the page!! source is ./drivers/gpu/drm/i915, dated October 2026, and the manual calls itself i915_request_active_engine(9) — periodt 💅✨