intel_guc_ggtt_offset(9)

💅 intel_guc_ggtt_offset(9) — like, the GGTT offset getter, bestie

okay so this is a page from the Kernel API Manual and it's all about intel_guc_ggtt_offset — a tiny little function that grabs the GGTT offset of a vma and validates it. yes, both. overachiever behavior honestly 🎀

---

✨ NAME ✨

intel_guc_ggtt_offset — get and validate the GGTT offset of @vma 💖

---

🦋 SYNOPSIS 🦋

u32 intel_guc_ggtt_offset (struct intel_guc *guc , struct i915_vma *vma
);

it takes two things and gives you back a u32. slay. ✨

---

🌸 ARGUMENTS 🌸

• guc — the intel_guc structure. that's the GuC guy himself 🫶
• vma — the i915 graphics virtual memory area. the actual memory vibe we're talking about 💅

---

💜 DESCRIPTION 💜

okay so here's the situation, and it's giving exclusive. GuC does not allow any gfx GGTT address that falls into the range [0, ggtt.pin_bias). periodt. that range is reserved — it's for Boot ROM, SRAM and WOPCM, so it's very much taken 🔥

so, currently, in order to exclude the [0, ggtt.pin_bias) address space from GGTT, all gfx objects used by GuC are allocated with intel_guc_allocate_vma and pinned with PIN_OFFSET_BIAS along with the value of ggtt.pin_bias. like, the whole workflow, no skipped steps. that's the whole trick 🧚

---

⭐ RETURN ⭐

the GGTT offset of the vma. that's it, that's the tea 👑

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/i915/gt/uc/intel_guc.h and struct intel_guc(9) — go read those too, iykyk 💖

---

ngl bestie this one's short but it matters — mess with that pin bias range and GuC will simply not have it 💀

okay bye ily, this page came from ./drivers/gpu/drm/i915/gt/uc, dated October 2026, and it's literally intel_guc_ggtt_offset(9) 🎀✨💅