i915_vma_offset(9)

✨ i915_vma_offset(9) ✨

okay so bestie, welcome to the Kernel API Manual 🎀 — this one's from the kernel source file ./drivers/gpu/drm/i915/i915_vma.h in the i915 vma family, and it's literally the glow-up for your offset needs 💅

---

🌸 NAME 🌸

i915_vma_offset — bestie's little helper that gets you the va offset of the vma 🦋

---

💖 SYNOPSIS 💖

u64 i915_vma_offset (const struct i915_vma *vma );

---

✨ ARGUMENTS ✨

• vma — the vma in question 🫶 (yes girl, the vma, that's her)

---

🧚 DESCRIPTION 🧚

so like, GPU virtual address space can be allocated with padding 🙈 — yes, padding, as in extra space, as in the whole thing isn't always just exactly what you asked for, iykyk.

This function gives you the effective virtual address offset the gpu should use to access the bound data ✨. It's the one you want, the actual address-y bit, not just the raw allocation vibes. no cap.

---

👑 RETURN 👑

The effective virtual address offset 💖 (a u64, if you were wondering, and of course you were)

---

🌈 SEE ALSO 🌈

Go check out the kernel file ./drivers/gpu/drm/i915/i915_vma.h and its besties:

• i915_vma_size(9)
• i915_vma_pin_iomap(9)
• i915_vma_unpin_iomap(9)
• i915_vma_pin_fence(9)
• i915_vma_unpin_fence(9)
• for_each_ggtt_vma(9)
• i915_vma_get_current_resource(9)

💀 seriously, read them, they're iconic.

---

and that's the whole page, bestie — periodt 💅 🌸

so anyway, this was served up fresh by ./drivers/gpu/drm/i915, dated October 2026 — that's the version and the source, we love to see it 💜 ✨ 🎀