i915_request_is_ready(9)

💖 i915_request_is_ready(9) 💖

okay so welcome to the Kernel API Manual page for i915_request_is_ready(9), bestie — it’s literally giving “check if the request is ready for execution” energy and we’re obsessed. 🎀

---

✨ NAME ✨

i915_request_is_ready — check if the request is ready for execution. periodt. 💅

---

🦋 SYNOPSIS 🦋

bool i915_request_is_ready (const struct i915_request *rq );

---

🌸 ARGUMENTS 🌸

• rq — the request. that’s the const struct i915_request * bestie, right there. 🫶

---

💜 DESCRIPTION 💜

okay so upon construction, the request is instructed to wait upon various signals before it is ready to be executed by the HW. like, we do not want to start execution and read data before it is written — no cap. in practice, this is controlled with a mixture of interrupts and semaphores. iconic combo, honestly. ✨

once the submit fence is completed, the backend scheduler will place the request into its queue and from there submit it for execution. so we can detect when a request is eligible for execution (and is under control of the scheduler) by querying where it is in any of the scheduler’s lists. literally just vibes-checking the scheduler’s lists. 👑

returns true if the request is ready for execution (it may be inflight), false otherwise. very demure, very mindful. 😌

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/gpu/drm/i915/i915_request.h — plus hwsp_seqno(9), i915_request_started(9), and i915_request_is_running(9). iykyk. 🧚

---

💖 cute little sign-off: this page’s source/version is ./drivers/gpu/drm/i915, dated October 2026, and it’s i915_request_is_ready(9) — byeee, slay, don’t forget the submit fence 🫶✨