xe_pt_entry_fn(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_pt_entry_fn(9) β€” the kernel API manual, but make it cute πŸŽ€

okay so bestie, quick vibe check: this is xe_pt_entry_fn, a gpu page-table-walk callback-function from the kernel API manual. yes the whole name is a mouthful, no we're not renaming it, periodt. ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

int xe_pt_entry_fn (struct xe_ptw *parent , pgoff_t offset , unsigned
int level , u64 addr , u64 next , struct xe_ptw **child , enum
page_walk_action *action , struct xe_pt_walk *walk );

like, literally that's the whole signature. she's long, she's iconic, she ate. πŸ’…


🌸 ARGUMENTS 🌸

  • parent β€” The parent page table. the main character of this whole situation tbh. πŸ‘‘
  • offset β€” The offset (number of entries) into the page table. yes, number of entries, not bytes β€” read the label bestie. πŸ“
  • level β€” The level of parent. she's got layers, okay. 🧚
  • addr β€” The virtual address. 🌈
  • next β€” The virtual address for the next call, or end address. iykyk. ⭐
  • child β€” Pointer to pointer to child page-table at this offset. The function may modify the value pointed to if, for example, allocating a child page table. (double pointer energy fr fr, she can change what's underneath. 🫢)
  • action β€” The walk action to take upon return. See <linux/pagewalk.h>. πŸ”₯
  • walk β€” The walk parameters. the whole itinerary, basically. πŸŽ€
ngl, action and walk are the ones you actually wanna go read up on β€” action points you at <linux/pagewalk.h>, and walk is carrying all the parameters. don't skip her. πŸ™ˆ

πŸ‘€ SEE ALSO πŸ‘‘

like go click around, it's giving lore deep-dive. πŸ’€βœ¨


and that's the page, bestie! 🌸 this one shipped out of ./drivers/gpu/drm/xe back in October 2026, and the manual labels it xe_pt_entry_fn(9) β€” same name up top, same name at the bottom, consistency queen πŸ‘‘πŸ’– πŸ¦‹

πŸ“¦ where this page comes from