drm_gpusvm_range_start(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’œ drm_gpusvm_range_start(9) β€” the kernel API manual, bestie edition

okay so picture this: you're deep in the kernel API manual (drm_gpusvm_range_start(9), yes that's the whole title, we're not shortening it) and you just need to know where a GPU SVM range starts. That's it. That's the whole function. She's a getter, she's iconic, she serves.


✨ NAME ✨

drm_gpusvm_range_start β€” literally just the GPU SVM range start address. no cap, that's the entire job description.


🌸 SYNOPSIS 🌸

unsigned long drm_gpusvm_range_start (struct drm_gpusvm_range *range );

look at her go 🫢 she takes one (1) pointer and hands you back an unsigned long. the way that signature is so clean, i'm obsessed.


πŸŽ€ ARGUMENTS πŸŽ€

  • range β€” pointer to the GPU SVM range πŸ’… that's the one you're asking about. give her the range, she gives you the start.

πŸ”₯ RETURN πŸ”₯

the GPU SVM range start address, returned as an unsigned long. that's it bestie, no hidden lore, no error codes, no surprises. she ate and left no crumbs ✨


πŸ¦‹ SEE ALSO πŸ¦‹

the whole friend group, fr fr. all of these live in the kernel file ./include/drm/drm_gpusvm.h:

like, the range start is giving main character energy but she did NOT get here alone πŸ’– go read the rest, iykyk.


ngl, drm_gpusvm_range_start(9) is the lowkey bestie of drm_gpusvm_range_end(9) β€” you literally cannot have one without the other. character development 🧚

and that's the page, bestie!! πŸ’–βœ¨πŸŽ€ shoutout to the source ./include/drm and the date October 2026 β€” that's the vibe check stamp, saving it for the group chat πŸ˜­πŸ‘‘πŸ’…

πŸ“¦ where this page comes from