i915_vma_unpin_iomap(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… i915_vma_unpin_iomap β€” the Kernel API Manual, bestie edition πŸŽ€

okay so you're in the i915_vma_unpin_iomap(9) page of the Kernel API Manual and honestly? it's a short one but it's important, so bestie please pay attention for like two seconds πŸ’–


✨ NAME ✨

i915_vma_unpin_iomap β€” literally just unpins the mapping you got back from i915_vma_iomap. that's it. that's the whole vibe. no cap 🫢


🌸 SYNOPSIS 🌸

void i915_vma_unpin_iomap (struct i915_vma *vma );

like, one function, one argument, zero drama πŸ”₯


πŸ¦‹ ARGUMENTS πŸ¦‹

  • vma β€” the VMA you want to unpin. yes, that VMA. the one you pinned earlier, bestie 😭

πŸ‘‘ DESCRIPTION πŸ‘‘

so here's the tea β˜• β€” this function unpins the VMA that was previously iomapped, the one you got from i915_vma_pin_iomap. it's the undoing of the doing. the closing of the loop. the "okay i'm done with this now" of it all πŸ’…

⚠️ read this part twice, fr fr: this function is only valid to call on a VMA that was previously iomapped by the caller with i915_vma_pin_iomap. like, you have to be the one who pinned it. don't be out here unpinning other people's iomaps, that's not the move πŸ™ˆ

🧚 SEE ALSO 🧚

Kernel file ./drivers/gpu/drm/i915/i915_vma.h β€” and go read these too, they're lowkey iconic:


🌈 and that's the page! 🌈

okay so this came out of ./drivers/gpu/drm/i915, dated October 2026, and it's been i915_vma_unpin_iomap(9) the whole time πŸ’œ slay, go unpin responsibly, mwah πŸ“βœ¨

πŸ“¦ where this page comes from