__drm_pagema...grate_to_ram(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __drm_pagema...grate_to_ram(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual, and specifically to this little internal icon, __drm_pagemap_migrate_to_ram. yes the header truncates it, yes it's giving "my name didn't fit in the group chat nickname field," we move.


✨ NAME ✨

__drm_pagemap_migrate_to_ram β€” migrate a GPU SVM range to RAM, but make it internal 🫢


🌸 SYNOPSIS 🌸

int __drm_pagemap_migrate_to_ram (struct vm_area_struct *vas , struct page *page , unsigned long fault_addr , unsigned long size );

like, that's the whole vibe right there, no cap.


πŸŽ€ ARGUMENTS πŸŽ€

  • vas β€” pointer to the VM area structure. literally the struct vm_area_struct, the main character of the address space.
  • page β€” pointer to the page being handled for the fault. the one going through it rn 😭
  • fault_addr β€” the fault address. yes bestie, exactly what it says.
  • size β€” size of the migration. how much we're moving, periodt.

πŸ¦‹ DESCRIPTION πŸ¦‹

so this is an internal function (iykyk, not for you to call directly, it's a backstage-pass situation) and what it does is perform the migration of the specified GPU SVM range to RAM. the way it does that:

  • it sets up the migration,
  • populates + dma maps RAM PFNs,
  • and then invokes the driver-specific operations for migration to RAM.

that's the whole pipeline, slay. πŸ”₯


⭐ RETURN ⭐

0 on success, negative error code on failure. so like, zero is the good ending πŸ’– and anything negative means something went off, check it.


🌈 SEE ALSO 🌈

bestie there are SO many siblings, buckle up 🧚:


ok that's the whole page, no notes πŸ’… go read the friends, they ate.

and finally, the cute little sign-off: this one lives in ./drivers/gpu/drm (yes, that's the source/version line bestie), dated October 2026, and the footer is also __drm_pagema...grate_to_ram(9) because the truncation is iconic at this point. bye pookie, happy migrating πŸ’œπŸŽ€

πŸ“¦ where this page comes from