xe_mem_pool_dump(9)
β¨ NAME β¨
okay so bestie, welcome to xe_mem_pool_dump(9) β that's the page, and it lives in the Kernel API Manual, and honestly it does exactly what it says on the tin π
xe_mem_pool_dump β Dump the state of the DRM MM manager for debugging.
πΈ SYNOPSIS πΈ
void xe_mem_pool_dump (struct xe_mem_pool *pool , struct drm_printer *p
);
like, that's the whole signature. two args, no return value, we move π«Ά
π ARGUMENTS π
poolβ the memory pool info be dumped. yes queen, this is the one getting dumped to the printer πpβ The DRM printer to use for output. this is where all the pretty text goes β¨
π¦ DESCRIPTION π¦
Only the drm managed region is dumped, not the state of the BOs or any other pool information.
ok so real talk β this is just the drm managed region, nothing else. no BO state, no other pool info. if you were hoping for the full tea, this is not that π
β RETURN β
None.
π₯ SEE ALSO π₯
Kernel file ./drivers/gpu/drm/xe/xe_mem_pool.c plus the whole friend group of related pages β go read them, they're iconic π
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_sync_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)
π§ and that's the page!! mwah π
okay so before you go β this whole thing ships from ./drivers/gpu/drm/xe, dated October 2026, and the page is xe_mem_pool_dump(9). periodt, no cap, go dump some pools responsibly ππ
π¦ 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