xe_pt_create(9)

💖 NAME 💖

okay so this is xe_pt_create(9) from the Kernel API Manual, and it's literally the page-table creation moment: create a page-table. bestie, we're making a page-table. that's the whole vibe. ✨

🦋 SYNOPSIS 🦋

struct xe_pt * xe_pt_create (struct xe_vm *vm , struct xe_tile *tile ,
unsigned int level , struct drm_exec *exec );

🌸 ARGUMENTS 🌸

• vm — the vm you're creating for. like, the whole vm situation. 🫶
• tile — the tile you're creating for. yes, that tile. 💅
• level — the page-table level. important number energy.
• exec — the drm_exec object used to lock the vm. lock it up, bestie 🔐

🎀 DESCRIPTION 🎀

So what this does is allocate and initialize a single struct xe_pt metadata structure. one whole metadata structure. iconic behavior, honestly.

It also creates the corresponding page-table bo, but — and this is the key part — it doesn't initialize it. nope. not yet. that's somebody else's job, iykyk.

If the level is grater than zero — yes, “grater” is the spelling in the original, and I am choosing peace 😭 — then it's assumed to be a directory page-table, and the directory structure is also allocated and initialized to NULL pointers. so many cute little nulls. NULL pointers everywhere. it's giving freshly swept directory. 🧹✨

⭐ RETURN ⭐

On success you get a valid struct xe_pt pointer. on error you get a Pointer error code. so like, check your return, bestie. no cap. 🫡

🌈 SEE ALSO 🌈

go look at these, bestie, they're all right here:

• Kernel file ./drivers/gpu/drm/xe/xe_pt.c
• xe_pt_populate_empty(9)
• xe_pt_shift(9)
• xe_pt_destroy(9)
• xe_pt_clear(9)
• Pagetable building(9)
• struct xe_pt_stage_bind_walk(9)
• xe_pt_stage_bind(9)
• xe_pt_nonshared_offsets(9)
• xe_pt_zap_ptes(9)
• xe_pt_zap_ptes_range(9)
• xe_pt_stage_unbind(9)
• xe_pt_update_ops_prepare(9)
• xe_pt_update_ops_run(9)
• xe_pt_update_ops_fini(9)
• xe_pt_update_ops_abort(9)

mwah 💋 this cutie came from source/version ./drivers/gpu/drm/xe, dated October 2026. periodt. 👑