svm_migrate_vram_to_ram(9)
π NAME π
okay bestie, this is svm_migrate_vram_to_ram(9), straight from the Kernel API Manual β¨ β and its whole main character job is to migrate svm range from device to system. That's the assignment, no cap. π«Ά
β¨ SYNOPSIS β¨
int svm_migrate_vram_to_ram (struct svm_range *prange , struct mm_struct
*mm , unsigned long start_mgr , unsigned long last_mgr , uint32_t
trigger , struct page *fault_page );
That's the exact signature, so keep it character for character if you're typing it out, fr fr. π
π§ ARGUMENTS π§
prangeβ the range structure, aka the thing getting migrated. main character energy πmmβ the process mm; if it'sNULL, usecurrent->mm. easy enough πstart_mgrβ the start page that needs to be migrated to sys ram. πlast_mgrβ the last page that needs to be migrated to sys ram. πtriggerβ the reason of migration. iykyk πfault_pageβ comes fromvmf->page,svm_migrate_to_ram; this is the CPU page fault callback. very demure, very mindful π
πΈ CONTEXT πΈ
Process context, bestie β the caller holds the mmap read lock and prange->migrate_mutex. do not forget either one, fr fr. π€
π RETURN π
0 β OK, otherwise error code. That's it. slay β¨
π¦ 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_vram(9)svm_migrate_to_ram(9)
go read these too, bestie β the lore is real. ππ
okay bye bestie π«Ά β source/version: ./drivers/gpu/drm/amd/amdkfd; date: October 2026. that's the whole svm_migrate_vram_to_ram(9) moment. mwah π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms