drm_gpuvm_exec_lock_range(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ drm_gpuvm_exec_lock_range ✨

okay so bestie, this is the drm_gpuvm_exec_lock_range page from the Kernel API Manual πŸ’… it's literally about prepping all your BOs in a range, no cap

SYNOPSIS

int drm_gpuvm_exec_lock_range (struct drm_gpuvm_exec *vm_exec , u64 addr , u64 range );

ARGUMENTS

  • vm_exec β€” the drm_gpuvm_exec wrapper, it's giving main character energy for the whole operation πŸŽ€
  • addr β€” the start address within the VA space, like where the vibe check begins ⭐
  • range β€” the range to iterate within the VA space, so how far we're going, periodt 🌸

DESCRIPTION

Acquires all dma-resv locks of all drm_gem_objects mapped between addr and addr + range. literally locking it all down bestie πŸ”₯

RETURN

0 on success, negative error code on failure. slay when it works, 😭 when it doesn't

SEE ALSO

okay so there's a LOT here but i got you bestie, every single one:

The Main Character Files πŸ“

  • Kernel file ./drivers/gpu/drm/drm_gpuvm.c

Concept Overviews πŸ¦‹

List Helper Besties πŸ’–

BO Vibes πŸ‘‘

Range & Resv Stuff πŸŽ€

Core GPUVm Functions ✨

Prepare Functions (the pregame) 🧚

Exec Lock Squad πŸ”’

BO Lifecycle Icons 🌈

GPUVA Mapping Crew πŸ—ΊοΈ

SM (Split/Merge) Operations πŸ’«


fr fr that's the whole list, every single one, no skips πŸ’…


Source vibe: ./drivers/gpu/drm β€’ Date: October 2026 β€’ that's the tea bestie 🫢

πŸ“¦ where this page comes from