xe_lrc_ctx_t...dw_ggtt_addr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

ok so this one's called xe_lrc_ctx_timestamp_udw_ggtt_addr β€” literally just "Get ctx timestamp udw GGTT address", that's the whole vibe, that's the assignment πŸŽ€

and yes bestie, this page lives in the Kernel API Manual, section 9, under the very cursed-looking name xe_lrc_ctx_t...dw_ggtt_addr(9) (the man page gods truncate long names, not me, don't come for me πŸ™ˆ).


✨ SYNOPSIS ✨

u32 xe_lrc_ctx_timestamp_udw_ggtt_addr (struct xe_lrc *lrc );

that's it. one function, one arg, returns a u32. she's lowkey minimal and I respect it 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • lrc β€” pointer to the lrc. yes, that's the entire description. it's giving "you already know what an lrc is or you don't" energy. it's a pointer to a struct xe_lrc, and that's all the manual is gonna give you πŸ’€

🌸 RETURN 🌸

the ctx timestamp udw GGTT address. returns it as a u32. that's it, that's the return, no cap ✨


πŸ‘‘ SEE ALSO πŸ‘‘

ok this is the part where the man page goes absolutely feral and links everything in the friend group πŸ’– and obviously the kernel file it actually lives in:

not me counting them all just so you wouldn't have to 😭 every single one is here, i did not skip a single bestie, periodt πŸ’…


and that's the whole page!! this one shipped out from ./drivers/gpu/drm/xe, dated October 2026, and it answers to xe_lrc_ctx_t...dw_ggtt_addr(9) if you ever need to find her again πŸŽ€πŸ’œ go forth and read your GGTT addresses, ily, bye πŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from