xe_mem_pool_...hadow_locked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 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:


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