xe_lrc_ctx_j...mp_ggtt_addr(9)

💅 NAME

xe_lrc_ctx_job_timestamp_ggtt_addr — bestie, this is the one that gets you the ctx job timestamp GGTT address ✨ (yes that's a whole mouthful, we know, but she ate)

So this page lives in the Kernel API Manual, and the header up top is just her name doing a little truncation moment: xe_lrc_ctx_j...mp_ggtt_addr(9). Cute, iconic, slay 💖

---

🌸 SYNOPSIS

u32 xe_lrc_ctx_job_timestamp_ggtt_addr (struct xe_lrc *lrc );

---

🎀 ARGUMENTS

• lrc — pointer to the lrc. that's it. that's the whole vibe check 🫶

---

⭐ RETURN

gives you back the ctx timestamp job GGTT address, as a u32. no cap, that's the whole dealio 💅

---

🦋 SEE ALSO

okay so here's the whole friend group, all of them (9) girlies, no gatekeeping:

• xe_gt_lrc_hang_replay_size(9)
• xe_lrc_reg_size(9)
• xe_lrc_engine_state_size(9)
• xe_lrc_ctx_timestamp_ggtt_addr(9)
• xe_lrc_ctx_timestamp_udw_ggtt_addr(9)
• xe_lrc_ctx_timestamp(9)
• xe_lrc_queue_timestamp(9)
• xe_lrc_ctx_job_timestamp(9)
• xe_default_lrc_update_memirq_regs_with_address(9)
• xe_lrc_update_memirq_regs_with_address(9)
• xe_lrc_setup_wa_bb_with_scratch(9)
• xe_lrc_set_multi_queue_priority(9)
• xe_lrc_create(9)
• xe_lrc_destroy(9)
• xe_lrc_update_hwctx_regs_with_address(9)
• xe_lrc_alloc_seqno_fence(9)
• xe_lrc_free_seqno_fence(9)
• xe_lrc_init_seqno_fence(9)
• xe_lrc_engine_id(9)
• xe_lrc_timestamp(9)
• xe_lrc_update_timestamp(9)
• xe_lrc_ring_is_idle(9)

and the kernel file herself, the main character: ./drivers/gpu/drm/xe/xe_lrc.c 🔥 (go read her, she's got lore)

---

ok so like slight warning bestie — this is the manual page, not a whole tutorial. the details above are literally all she said. don't be out here inventing behaviour, mkay? 🙈

---

n e wayz, that's the page! brought to you from ./drivers/gpu/drm/xe, dated October 2026, and yes the footer still spells her xe_lrc_ctx_j...mp_ggtt_addr(9) because the truncation is part of the brand now 💜 bye bestie, ily, go read your man pages 🧚✨