i915_vma_size(9)

✨ i915_vma_size ✨

okay so real quick — this is i915_vma_size(9) from the Kernel API Manual, and honestly? it's a tiny little function that does exactly one thing and does it slay 💅

---

🎀 NAME 🎀

i915_vma_size — literally just: get the va range size of the vma 🦋

🌸 SYNOPSIS 🌸

u64 i915_vma_size (const struct i915_vma *vma );

💖 ARGUMENTS 💖

• vma — the vma bestie. that's it. that's the whole argument. the vma in question 💜

🦋 DESCRIPTION 🦋

so here's the tea 🍓 — GPU virtual address space can be allocated with padding. like, the address space people be reserving more room than they actually need, no cap. this function hands you back the effective virtual address range size, with that padding subtracted out. so you get the real number, not the inflated one ✨ iconic behavior honestly.

⭐ RETURN ⭐

the effective virtual address range size. that's the whole vibe check. 🫶

🔥 SEE ALSO 🔥

kernel file ./drivers/gpu/drm/i915/i915_vma.h — and yes, the whole friend group is here:

• i915_vma_offset(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)

---

ngl this one's short but it ate. go read the header file, iykyk 👑

---

and that's the whole page diva 💅 — brought to you by ./drivers/gpu/drm/i915, dated October 2026, main character energy only 🌈🎀✨