hwsp_seqno(9)

💅 hwsp_seqno(9) — the kernel API manual, but make it make sense

okay bestie, so this is hwsp_seqno(9) from the Kernel API Manual, and honestly? It's giving "tiny function, big lore" ✨ Let's get into it.

---

🎀 NAME 🎀

hwsp_seqno — literally just the current breadcrumb value in the HW status page. that's it. that's the whole vibe 🍓

---

✨ SYNOPSIS ✨

u32 hwsp_seqno (const struct i915_request *rq );

she's small, she's u32, she takes one const struct i915_request * and she's out. main character energy honestly 👑

---

🫶 ARGUMENTS 🫶

• rq — the request, and you're gonna chase it to find the relevant HW status page. yes, chase. it's a whole quest bestie, but the reward is a breadcrumb so like… worth it 💖

---

🌸 DESCRIPTION 🌸

okay so the emphasis in the naming here is everything, so pay attention: hwsp_seqno is NOT a property of the request. nope. it's an indication of the current HW state, associated with this request. so its value is gonna change as the GPU executes more requests — it's alive, it's moving, it's lowkey not stable 😭 don't be weird about that.

What she returns: the current breadcrumb value in the associated HW status page (or the local timeline's equivalent, for when your fave isn't available, we don't judge) for this request 🦋

So here's the tea — the request itself has the associated breadcrumb value of rq->fence.seqno. And when the HW status page has that breadcrumb or later? boom. this request is complete. slay. periodt. ✅

ngl, the top-level takeaway is: this isn't "what is the request" it's "where is the hardware right now", and comparing those two is the whole entire bit 🔥

---

👀 SEE ALSO 👀

• Kernel file ./drivers/gpu/drm/i915/i915_request.h
• i915_request_started(9)
• i915_request_is_running(9)
• i915_request_is_ready(9)

---

🌈 the cute sign-off 🌈

this absolute icon of a page lives in ./drivers/gpu/drm/i915, and it's dated October 2026 — yes, she's from the future, we don't ask questions 💜 iykyk. bye bestie, go check your breadcrumbs 🧚💅