xe_guc_engin..._total_ticks(9)

💅 xe_guc_engine_activity_total_ticks — get engine total ticks ✨

Okay so bestie, welcome to the kernel API manual for xe_guc_engine_activity_total_ticks(9) — yes the whole name is a mouthful, no we're not shortening it, it's iconic and it knows it. This is a section 9 (kernel API) page, and it's literally just one little function that tells you how many ticks an engine got. Let's get into it 🎀

---

🌸 NAME 🌸

xe_guc_engine_activity_total_ticks — get engine total ticks. That's the whole vibe. It gets. Engine. Total. Ticks. 🦋

---

✨ SYNOPSIS ✨

u64 xe_guc_engine_activity_total_ticks (struct xe_guc *guc , struct
xe_hw_engine *hwe , unsigned int fn_id );

Notice the return type is u64, so she's coming back with a big ol' number. Very main character energy 👑

---

🫶 ARGUMENTS 🫶

Three args, all of them essential, no cap:

• guc — the GuC object. Like, the whole GuC. Yes that one 💜
• hwe — the hw_engine object. The engine in question, the one we're snooping on 🔥
• fn_id — the function id to report on. Gotta tell her which function you're asking about, she's not a mind reader 😭

---

⭐ RETURN ⭐

The accumulated quanta of ticks allocated for the engine. That's it, that's the answer — a u64 of accumulated quanta of ticks, allocated, for the engine. Slay. ✨

---

🦋 SEE ALSO 🦋

Bestie, the friend group is big and they all show up:

• Kernel file ./drivers/gpu/drm/xe/xe_guc_engine_activity.c — the source, go read her 💖
• xe_guc_engine_activity_active_ticks(9)
• xe_guc_engine_activity_supported(9)
• xe_guc_engine_activity_function_stats(9)
• xe_guc_engine_activity_enable_stats(9)
• xe_guc_engine_activity_init(9)

Go check those out, iykyk 🌈

---

Reminder: this page is from ./drivers/gpu/drm/xe, dated October 2026, and it's filed under xe_guc_engin..._total_ticks(9) — yes the title is truncated with ... in the footer, and honestly? She ate. Periodt. 💅🌸🎀