xe_mem_pool_...hadow_locked(9)
πΈ NAME πΈ
xe_mem_pool_sync_shadow_locked β ok so this one copies a node from the primary pool over to the shadow pool, bestie π
that's literally the whole gig
(this little cutie lives in the Kernel API Manual, section 9 β yes, xe_mem_pool_...hadow_locked(9), she's an icon β¨)
π SYNOPSIS π
void xe_mem_pool_sync_shadow_locked (struct xe_mem_pool_node *node );
π«Ά ARGUMENTS π«Ά
nodeβ the node that was allocated in the memory pool, that's the one we're working with π
π¦ DESCRIPTION π¦
So what it does: it copies the specified batch buffer from the primary pool over to the shadow pool π literally a glow-up relocation, no cap.
β οΈ Important caveat, don't skip this one: Swap_guard must be held the whole time β it's what keeps things in sync with any concurrent swap operations happening at the same time. Not optional, fr fr π
β RETURN β
None. Nope. Nothing. Zero. She returns void and she's at peace with that π
π SEE ALSO π
Kernel file ./drivers/gpu/drm/xe/xe_mem_pool.c, plus the whole friend group:
struct xe_mem_pool(9)xe_mem_pool_init(9)xe_mem_pool_sync(9)xe_mem_pool_swap_shadow_locked(9)xe_mem_pool_gpu_addr(9)xe_mem_pool_cpu_addr(9)xe_mem_pool_bo_swap_guard(9)xe_mem_pool_bo_flush_write(9)xe_mem_pool_bo_sync_read(9)xe_mem_pool_alloc_node(9)xe_mem_pool_insert_node(9)xe_mem_pool_free_node(9)xe_mem_pool_node_cpu_addr(9)xe_mem_pool_dump(9)
okay that's the whole page, ily, go hold that swap_guard π
this masterpiece came from the kernel source at ./drivers/gpu/drm/xe, dated October 2026, and yes the footer still says xe_mem_pool_...hadow_locked(9) β she ate and left no crumbs πβ¨
π¦ 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