drm_gem_ttm_mmap(9)
π
drm_gem_ttm_mmap(9) β the mmap bestie for your ttm_buffer_object
okay so welcome to the Kernel API Manual page for drm_gem_ttm_mmap, bestie π this is a real one, it lives in section 9 of the manual, and it's literally just here to let you mmap a &ttm_buffer_object. that's the vibe. no cap.
β¨ NAME β¨
drm_gem_ttm_mmap β mmap &ttm_buffer_object π«Ά
π SYNOPSIS π
int drm_gem_ttm_mmap (struct drm_gem_object *gem , struct vm_area_struct *vma );
that's it, that's the whole signature. two args, one int coming back at you π
πΈ ARGUMENTS πΈ
gemβ a GEM object. yes bestie, thestruct drm_gem_object *one, right there in the synopsis.vmaβ the vm area. that's yourstruct vm_area_struct *. it's giving "the memory region we're mapping into" energy π¦
π DESCRIPTION π
ok so here's the whole tea: this function can be used as the drm_gem_object_funcs.mmap callback β¨ that's literally the entire description. it's a helper, it does the mmap thing, you plug it into that callback slot, and you're slaying π₯
ngl, it's a short description β but every word of it is load-bearing, so don't skip it π
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/drm_gem_ttm_helper.coverview(9) drm_gem_ttm_print_info(9)drm_gem_ttm_vmap(9)drm_gem_ttm_vunmap(9)drm_gem_ttm_dumb_map_offset(9)
go read those too, iykyk π the whole ttm helper family is lowkey iconic.
and that's the page, bestie π fr fr. this one came from ./drivers/gpu/drm and it's dated October 2026 β so when you're out here mmapping your &ttm_buffer_object, just remember who told you: me, your fave manual page, drm_gem_ttm_mmap(9) π
β¨π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms