i915_vma_ge...ent_resource(9)

📦 version 7.3.1, in nixpkgs unstable

💖 NAME 💖

i915_vma_get_current_resource — bestie, this is the one that gets the current resource of the vma. We're in the Kernel API Manual and it's giving very "I live in the kernel tree" energy. 💅

✨ SYNOPSIS ✨

struct i915_vma_resource * i915_vma_get_current_resource (struct
i915_vma *vma );

🎀 ARGUMENTS 🎀

  • vma — the vma you're pulling the current resource from. That's the one, no cap. 🫶

🌸 DESCRIPTION 🌸

Okay so here's the tea: it's illegal to call this function if the vma is not bound. Not "illegal" like cops-and-robbers illegal — illegal like do not do this, bestie. 😭 Vibe check your vma first. Is it bound? Because this function is assuming yes.

Fr fr, do not call this on an unbound vma. Periodt. 💀

🔥 RETURN 🔥

A refcounted pointer to the current vma resource of the vma — assuming the vma is bound. That "assuming" is doing a lot of heavy lifting, so don't forget it. ✨

🦋 SEE ALSO 🦋

The kernel file is ./drivers/gpu/drm/i915/i915_vma.h, and the squad pulls up like:

Mwah 💋 — this page came from ./drivers/gpu/drm/i915, dated October 2026. That's the whole manual page, bestie, no cap. 🫶🎀

📦 where this page comes from