drm_vma_offset_lock_lookup(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_vma_offset_lock_lookup(9) β€” the Kernel API Manual tea β˜•

okay so bestie, we're in the Kernel API Manual today and the function on the menu is drm_vma_offset_lock_lookup β€” say that five times fast, i dare you 🫢


✨ NAME ✨

drm_vma_offset_lock_lookup β€” lock lookup for extended private use πŸ”’


✨ SYNOPSIS ✨

void drm_vma_offset_lock_lookup (struct drm_vma_offset_manager *mgr );

✨ ARGUMENTS ✨

  • mgr β€” the manager object, aka the main character of this whole operation πŸ‘‘

✨ DESCRIPTION ✨

So what does it do? It locks the VMA manager for extended lookups. That's it, that's the vibe. πŸ”

While you're holding this lock, only locked VMA function calls are allowed. Literally everyone else? Blocked from VMA until you release it via drm_vma_offset_unlock_lookup. no cap, the door stays shut 😀

Use this if you need to take a reference to the objects returned by drm_vma_offset_lookup_locked before releasing this lock again. grab your reference while the lock is still yours, bestie πŸ’–

⚠️ This lock must not be used for anything else than extended lookups. Periodt. You must not call any other VMA helpers while holding this lock. none. zero. don't even think about it πŸ™ˆ

✨ NOTE ✨

You're in atomic-context while holding this lock! πŸ’€ like, for real, act accordingly.


✨ SEE ALSO ✨

Kernel file ./include/drm/drm_vma_manager.h

Also go check out these icons 🌟:


and that's the whole page, bestie πŸŽ€ this came to you from ./include/drm, dated October 2026, and it's drm_vma_offset_lock_lookup(9) forever and always πŸ’œ mwah, go lock something responsibly πŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from