drm_pagemap...te_to_devmem(9)

📦 version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay bestie, this is the drm_pagemap_migrate_to_devmem(9) page from the Kernel API Manual — and it's literally about migrating a struct mm_struct range to device memory 💖

🦋 SYNOPSIS 🦋

the whole call looks like this:

int drm_pagemap_migrate_to_devmem (struct drm_pagemap_devmem
       *devmem_allocation , struct mm_struct *mm , unsigned long start ,
       unsigned long end , const struct drm_pagemap_migrate_details *mdetails
       );

🎀 ARGUMENTS 🎀

  • devmem_allocation — the device memory allocation you're migrating to 💅 The caller should hold a reference to the device memory allocation, and that reference is consumed by this function even if it returns with an error. yes, consumed even on error — no take-backs 😭
  • mm — pointer to the struct mm_struct.
  • start — start of the virtual address range to migrate.
  • end — end of the virtual address range to migrate.
  • mdetails — the details that govern the migration.

🌸 DESCRIPTION 🌸

This function migrates the specified virtual address range to device memory. It does the necessary setup and invokes the driver-specific operations for migration to device memory. Expected to be called while holding the mmap lock in at least read mode 👑

💀 NOTE 💀

The timeslice_ms parameter can typically be used to force data to remain in pagemap pages long enough for a GPU to perform a task and to prevent a migration livelock. One alternative would be for the GPU driver to block in a mmu_notifier for the specified amount of time, but adding the functionality to the pagemap is likely nicer to the system as a whole ✨

🔥 RETURN 🔥

0 on success, negative error code on failure 🫶

🌈 SEE ALSO 🌈

Kernel file: ./drivers/gpu/drm/drm_pagemap.c — and the whole reference squad is:

and that's the whole page, bestie 💖 this one came from ./drivers/gpu/drm, dated October 2026 — mwah 💅

📦 where this page comes from