__drm_gpusvm_range_next(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __drm_gpusvm_range_next(9) β€” kernel API manual, bestie edition ✨

okay so welcome to the Kernel API Manual page for __drm_gpusvm_range_next β€” yes it's got the double underscore, yes it's a little intimidating, no you're gonna be fine, i promise 🫢


🌸 NAME 🌸

__drm_gpusvm_range_next β€” literally just "get the next GPU SVM range in the list", that's it, that's the whole job πŸ’«


✨ SYNOPSIS ✨

struct drm_gpusvm_range * __drm_gpusvm_range_next (struct
drm_gpusvm_range *range );

like… look at her. one argument. one return. main character energy honestly πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • range β€” a pointer to the current GPU SVM range. that's your "i am here" dot on the map, bestie πŸ“

πŸ¦‹ RETURN πŸ¦‹

so what do you get back?

  • A pointer to the next drm_gpusvm_range if available ✨ slay, there's more list to walk
  • Or NULL in two very specific situations, and i need you to clock both of them:
    • if the current range is the last one β€” you've hit the end of the list, no more range for you 😭
    • or if the input range is NULL β€” you handed it nothing, it hands you nothing back, fair's fair πŸ’€
no cap, that NULL-in-NULL-out case is not a bug, it's a documented mood. respect it πŸ™ˆ

🌈 SEE ALSO 🌈

the whole friend group, gathered for your convenience 🧚 β€” and yes, it's a long group chat, we're not skipping anyone:


okay that's the whole page, you ate that πŸ’… and before you go β€” this lil masterpiece lives in ./include/drm, the version is October 2026, and it says __drm_gpusvm_range_next(9) at the bottom too because the header and footer are both obsessed with her. periodt πŸ“πŸ’œ

πŸ“¦ where this page comes from