xe_mem_pool_sync(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ xe_mem_pool_sync ✨

okay so this is the xe_mem_pool_sync(9) page from the Kernel API Manual, and honestly bestie it's a little one but it's important πŸ’…

🌸 NAME 🌸

xe_mem_pool_sync β€” literally copies the entire contents of the main pool over to the shadow pool. that's it. that's the whole vibe 🫢

πŸŽ€ SYNOPSIS πŸŽ€

void xe_mem_pool_sync (struct xe_mem_pool *pool );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • pool β€” the memory pool that's holding both the primary and the shadow BOs. she's the main character here, we just hand her over πŸ’–

🌈 DESCRIPTION 🌈

so what this does is copy the entire contents of the primary pool into the shadow pool. like, all of it. every last bit. no cap ✨

now here's the thing you actually need to know: you must do this after xe_mem_pool_init, and you must pass the XE_MEM_POOL_BO_FLAG_INIT_SHADOW_COPY flag when you do it β€” that flag is what makes sure the shadow pool ends up with the same initial contents as the primary pool. it's giving "matching outfits on day one" πŸŽ€

and then? after this first big sync is done, clients are free to sync the shadow pool with the primary pool however they like β€” on a node basis β€” using xe_mem_pool_sync_shadow_locked, whenever they need it. so this function is the one-time full copy, and after that it's piece by piece, iykyk πŸ’…

⭐ RETURN ⭐

None. nothing. nada. she returns void, she does the thing, she moves on 🧚

πŸ”₯ SEE ALSO πŸ”₯


okay that's the whole page bestie, go sync some pools πŸ’œ

this lil icon comes to you from ./drivers/gpu/drm/xe and it's dated October 2026 β€” periodt, slay, bye πŸ‘‘

πŸ“¦ where this page comes from