svm_migrate_ram_to_vram(9)

💅 svm_migrate_ram_to_vram(9)

okay so bestie, welcome to the Kernel API Manual — yes that's the manual name, we're in the big-leagues kernel docs now ✨

🌸 NAME 🌸

svm_migrate_ram_to_vram — bestie this literally migrates an svm range from system memory to device memory, and ngl that's the whole vibe 🦋

✨ SYNOPSIS ✨

int svm_migrate_ram_to_vram (struct svm_range *prange , uint32_t
best_loc , unsigned long start_mgr , unsigned long last_mgr , struct
mm_struct *mm , uint32_t trigger );

like, that's the whole signature, no cap — copy it exactly bestie 💅

🎀 ARGUMENTS 🎀

• prange — the range structure, the main character of this whole operation 👑
• best_loc — the device we're migrating to, i.e. the destination of the whole glow-up 🦋
• start_mgr — start page to migrate, where the journey begins 🌸
• last_mgr — last page to migrate, where the journey ends 🎀
• mm — the process mm structure, yes that one, the memory-map one 💜
• trigger — the reason of migration, like why are we doing this, what's the lore 😭

🔥 CONTEXT 🔥

So here's the thing bestie — this runs in process context, and the caller has to hold the mmap read lock, the svms lock, and the prange lock. All three. Not optional. The way that's non-negotiable fr fr 🔒

bestie do NOT call this without holding all three locks, that's giving undefined-behaviour disaster energy 💀

⭐ RETURN ⭐

0 — OK, slay, it worked 🎉

otherwise — an error code, so like, it didn't work, and you get to find out why 🙈

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/amd/amdkfd/kfd_migrate.c — the source, iykyk 📁
• svm_migrate_copy_memory_gart(9)
• svm_migrate_copy_done(9)
• svm_migrate_vma_to_ram(9)
• svm_migrate_vram_to_ram(9)
• svm_migrate_vram_to_vram(9)
• svm_migrate_to_ram(9)

like, the whole migrate friend group, obsessed 🫶

---

and that's the page bestie!! 💖 it lives under ./drivers/gpu/drm/amd/amdkfd, and this lil edition is dated October 2026 — see you in the next svm_migrate_ram_to_vram(9) era, periodt ✨💅