__drm_gpusvm_range_remove(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 __drm_gpusvm_range_remove β€” Kernel API Manual ✨

okay so bestie, welcome to the __drm_gpusvm_range_remove(9) page from the Kernel API Manual πŸ’… this one lives in the DRM/GPU corner of the kernel and it's honestly a little baddie of a macro. let's get into it 🫢


✨ NAME ✨

__drm_gpusvm_range_remove β€” Remove GPU SVM range πŸ§ΉπŸ’–


✨ SYNOPSIS ✨

void __drm_gpusvm_range_remove (struct drm_gpusvm_notifier *notifier ,
       struct drm_gpusvm_range *range );

like, that's the whole signature. two pointers, zero drama. no cap πŸ‘‘


✨ ARGUMENTS ✨

  • notifier β€” Pointer to the GPU SVM notifier structure πŸ“ like, this is the notifier bestie we're operating on
  • range β€” Pointer to the GPU SVM range structure πŸ“ and this is the range that's getting yeeted

✨ DESCRIPTION ✨

okay so the actual tea β˜•: this macro removes the GPU SVM range from the notifier RB tree and from the list. both. not one, not the other β€” both, periodt πŸ’€βœ¨

it's giving cleanup era, it's giving tidy vibes, it's giving "get this range out of my data structures" πŸ”₯


✨ SEE ALSO ✨

bestie there are so many friends on this list, it's giving whole-group-chat energy πŸ˜­πŸ’– all of these are (9) sections unless noted:


ngl, go read the actual kernel docs for the deep lore β€” this page is just the vibe check πŸ’«

and that's the whole page, bestie πŸ¦‹ mwah πŸ’‹ this one shipped from ./drivers/gpu/drm and it's dated October 2026 β€” so like, from the future?? iconic behavior honestly 🌈⭐ see u in the next manpage πŸ’œ

πŸ“¦ where this page comes from