svm_migrate_copy_done(9)
π NAME π
svm_migrate_copy_done β bestie, this one waits for the memory copy sdma to be done β¨
So this page lives in the Kernel API Manual (yes, that's the manual name, we're fancy now π), and it's all about one little function that waits on a fence. Slay.
πΈ SYNOPSIS πΈ
int svm_migrate_copy_done (struct amdgpu_device *adev , struct dma_fence
*mfence );
That's the whole vibe. Two args, one int, zero drama π
π ARGUMENTS π
adevβ the amdgpu device that the sdma memory copy is executing on. Like, this is the GPU doing the actual work, okay? π«Άmfenceβ the migrate fence. The fence we're waiting on. Iconic little synchronization object π₯
π¦ DESCRIPTION π¦
Okay so the whole point: this function waits for the dma fence to be signaled. That's it. That's the job π
And if the copy got split into multiple sdma operations, then the fence you're passing in here is the last sdma operation's fence β like the final boss of the copy chain π
π CONTEXT π
Called after svm_migrate_copy_memory. That's the context, bestie. Don't call it before, that's not the vibe π
β RETURN β
0β success β¨- otherwise β an error code from dma fence signal π
So yeah, zero means we ate, anything else means the fence said no π
π SEE ALSO π
Kernel file ./drivers/gpu/drm/amd/amdkfd/kfd_migrate.c
And the whole friend group of related functions, no cap:
svm_migrate_copy_memory_gart(9)svm_migrate_ram_to_vram(9)svm_migrate_vma_to_ram(9)svm_migrate_vram_to_ram(9)svm_migrate_vram_to_vram(9)svm_migrate_to_ram(9)
Go read those too, iykyk π§
Alright bestie, that's the page π This little icon was brought to you by ./drivers/gpu/drm/amd/amdkfd, dated October 2026, and yes β the page is literally called svm_migrate_copy_done(9). Periodt π
β¨
π¦ 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