xe_mem_pool_...hadow_locked(9)

📦 version 7.3.1, in nixpkgs unstable

💅 xe_mem_pool_swap_shadow_locked(9)

okay so this is a page straight out of the Kernel API Manual — the xe_mem_pool_...hadow_locked(9) one, bestie, and it's lowkey iconic. it's all about the xe memory pool and how we do the classic switcheroo on buffer objects. buckle up 🎀

✨ NAME ✨

xe_mem_pool_swap_shadow_locked — literally swaps the primary BO with the shadow BO. that's it, that's the whole vibe. 🦋

🌸 SYNOPSIS 🌸

void xe_mem_pool_swap_shadow_locked (struct xe_mem_pool *pool );

no cap, that's the signature. short, sweet, and ready to rearrange your BOs. ✨

🫶 ARGUMENTS 🫶

  • pool — the memory pool that's holding both the primary and the shadow BOs. she's the main character here, she contains multitudes 💖

🔥 DESCRIPTION 🔥

okay bestie, so what this does: it swaps the primary buffer object with the shadow buffer object inside the mem pool. the way that this works is genuinely clever — it lets you do atomic updates to the contents of the primary BO by first writing to the shadow BO and then swapping it with the primary BO. write first, swap second, atomicity preserved, we love to see it. 💅

⚠️ but listen — Swap_guard must be held to make sure everything stays synced up with any concurrent swap operations. do not skip the guard, bestie, that's a whole mess waiting to happen. 😭

💀 RETURN 💀

None. nothing comes back. void. empty. she gives nothing and that's on purpose 🎀

🧚 SEE ALSO 🧚

kernel file ./drivers/gpu/drm/xe/xe_mem_pool.c, plus the whole squad:

and that's the whole page, bestie — go read the friends, they're all waiting 💜

mwah 💋 this came from ./drivers/gpu/drm/xe and is dated October 2026 — the xe_mem_pool_...hadow_locked(9) chronicles, signed, sealed, delivered ✨🎀🦋

📦 where this page comes from