svm_migrate_vram_to_vram(9)

okay bestie, welcome to svm_migrate_vram_to_vram(9) from the Kernel API Manual 💖 this one is all about migrating an svm range from device to device, and it is giving niche-but-iconic kernel energy ✨

🦋 NAME 🦋

svm_migrate_vram_to_vram — migrate svm range from device to device 💅

🌈 SYNOPSIS 🌈

int svm_migrate_vram_to_vram (struct svm_range *prange , uint32_t
       best_loc , unsigned long start , unsigned long last , struct mm_struct
       *mm , uint32_t trigger );

🎀 ARGUMENTS 🎀

• prange — range structure 🫶
• best_loc — the device to migrate to 🌟
• start — start page need be migrated to sys ram 🍓
• last — last page need be migrated to sys ram 🍓
• mm — process mm, use current->mm if NULL 🧚
• trigger — reason of migration 🔥

🧚 CONTEXT 🧚

Process context, and the caller must hold the mmap read lock, the svms lock, and the prange lock — yes, all of them, no skipping the lock vibe check 🔒✨

💜 DESCRIPTION 💜

okay so here’s the tea: it migrates all vram pages in prange to sys ram, then migrates the [start, last] pages from sys ram to the gpu node best_loc 🌈💫

⭐ RETURN ⭐

• 0 — OK, otherwise error code 👑

👑 SEE ALSO 👑

• Kernel file: ./drivers/gpu/drm/amd/amdkfd/kfd_migrate.c 📁
• svm_migrate_copy_memory_gart(9)
• svm_migrate_copy_done(9)
• svm_migrate_ram_to_vram(9)
• svm_migrate_vma_to_ram(9)
• svm_migrate_vram_to_ram(9)
• svm_migrate_to_ram(9)

mwah 💋 that’s the whole page, bestie — brought to you by ./drivers/gpu/drm/amd/amdkfd, dated October 2026, and filed under svm_migrate_vram_to_vram(9). go migrate responsibly 🫶✨