evergreen_copy_dma(9)

evergreen_copy_dma(9) 💅

okay bestie, welcome to the evergreen_copy_dma(9) manual page — it’s giving kernel API realness, and we’re gonna get through it together. no cap. ✨

🌸 NAME 🌸

evergreen_copy_dma — copy pages using the DMA engine. that’s the whole main-character summary, periodt. 💖

✨ SYNOPSIS ✨

struct radeon_fence * evergreen_copy_dma (struct radeon_device *rdev ,
uint64_t src_offset , uint64_t dst_offset , unsigned num_gpu_pages ,
struct dma_resv *resv );

🎀 ARGUMENTS 🎀

• rdev — a radeon_device pointer. literally the device bestie.
• src_offset — src GPU address. the “from” coordinate, if you will. 🎯
• dst_offset — dst GPU address. the “to” coordinate. iconic destination energy.
• num_gpu_pages — number of GPU pages to xfer. yes, xfer is the word here, we respect it. 🫶
• resv — reservation object with embedded fence. very “there’s a fence in this reservation object” of it all. 🔥

🦋 DESCRIPTION 🦋

Copy GPU paging using the DMA engine (evergreen-cayman). that’s the assignment, and it ate. 💅

It’s used by the radeon ttm implementation to move pages if registered as the asic copy callback. so like — if the callback situation is registered, the radeon ttm implementation uses this to move pages. iykyk. 🧚

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/radeon/evergreen_dma.c
• evergreen_dma_fence_ring_emit(9)
• evergreen_dma_ring_ib_execute(9)
• evergreen_dma_is_lockup(9)

this page is brought to you by ./drivers/gpu/drm/radeon, October 2026, and the manual name is evergreen_copy_dma(9) — periodt. 🫶💖