drm_gpusvm_get_pages(9)

📦 version 7.3.1, in nixpkgs unstable

💅 drm_gpusvm_get_pages(9)

okay so bestie, welcome to the Kernel API Manual — this one's drm_gpusvm_get_pages, and it's genuinely the moment where your CPU pages get their whole GPU-era glow-up ✨

🎀 NAME 🎀

drm_gpusvm_get_pages — grab pages and populate the GPU SVM pages struct, no cap.

🦋 SYNOPSIS 🦋

int drm_gpusvm_get_pages (struct drm_gpusvm *gpusvm , struct
       drm_gpusvm_pages *svm_pages , struct mm_struct *mm , struct
       mmu_interval_notifier *notifier , unsigned long pages_start , unsigned
       long pages_end , const struct drm_gpusvm_ctx *ctx );

like, look at that signature. seven whole parameters. main character energy fr fr 💅

🌸 ARGUMENTS 🌸

  • gpusvm — Pointer to the GPU SVM structure. your home base 🏠
  • svm_pages — The SVM pages to populate. This will contain the dma-addresses — so yeah, it comes back with the goods 💖
  • mm — The mm corresponding to the CPU range. the vibe check for which address space we're in.
  • notifier — The corresponding notifier for the given CPU range. it's giving "I'll let you know if anything moves" 📣
  • pages_start — Start CPU address for the pages.
  • pages_end — End CPU address for the pages (exclusive). exclusive!! important!! don't @ me 🙈
  • ctx — GPU SVM context.

✨ DESCRIPTION ✨

This function gets and maps pages for the CPU range and ensures they are mapped for DMA access.

that's it. that's the whole thing. it lowkey ate and left no crumbs — CPU range in, DMA-mapped pages out, and everything in between is handled for you 🫶

🔥 RETURN 🔥

0 on success, negative error code on failure. classic. iconic. periodt. 👑

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/drm_gpusvm.c

like, that's a whole friend group and you're gonna want to know all of them 💜

and that's the page!! 🌟 this lil manpage lives in ./drivers/gpu/drm, and it's stamped October 2026 — mwah, go read the actual source, ily, bye 🧚💖

📦 where this page comes from