xe_migrate_from_vram(9)

💖 NAME 💖

okay so bestie, this is xe_migrate_from_vram(9) from the Kernel API Manual, and it is literally the Migrate from VRAM moment. Function name: xe_migrate_from_vram; short description: Migrate from VRAM. Slay, periodt.

✨ SYNOPSIS ✨

Here’s the signature, exactly as written, no edits:

struct dma_fence * xe_migrate_from_vram (struct xe_migrate *m , unsigned long npages , u64 src_addr , struct drm_pagemap_addr *dst_addr , struct dma_fence *deps );

No cap, that’s the whole signature. 💅

🎀 ARGUMENTS 🎀

• m — the migration context. Main character struct, fr.
• npages — number of pages to migrate. Count ‘em.
• src_addr — device physical address of VRAM (source of migrate). This is where the copy is coming from.
• dst_addr — array of DMA information (destination of migrate). This is where it’s going.
• deps — struct dma_fence representing the dependencies that need to be signaled before migration. Gotta wait for the vibes to line up first.

🦋 DESCRIPTION 🦋

Copy from a VRAM device physical address to an array of DMA addresses. That’s the whole glow-up: source is VRAM physical address, destination is that array of DMA info. ✨

💫 RETURN 💫

Returns a DMA fence for the migrate to signal completion on success, and ERR_PTR on failure. So if it works, you get the fence; if not, ERR_PTR is the plot twist. 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/xe/xe_migrate.c, plus all these besties:

• struct xe_migrate(9)
• xe_migrate_alloc(9)
• xe_migrate_init(9)
• xe_migrate_copy(9)
• xe_migrate_resolve(9)
• xe_migrate_lrc(9)
• xe_migrate_ccs_rw_copy(9)
• xe_migrate_ccs_rw_copy_clear(9)
• xe_migrate_exec_queue(9)
• xe_migrate_vram_copy_chunk(9)
• xe_migrate_clear(9)
• xe_migrate_update_pgtables(9)
• xe_migrate_wait(9)
• xe_migrate_to_vram(9)
• xe_migrate_access_memory(9)
• xe_migrate_job_lock(9)
• xe_migrate_job_unlock(9)
• xe_migrate_job_lock_assert(9)

xoxo, your xe_migrate_from_vram(9) bestie — source/version: ./drivers/gpu/drm/xe, date: October 2026 💖