xe_guc_engi...active_ticks(9)

📦 version 7.3.1, in nixpkgs unstable

✨ xe_guc_engine_activity_active_ticks(9) ✨

okay bestie, welcome to the Kernel API Manual 💖 we're talking about xe_guc_engine_activity_active_ticks today and honestly? it's giving "small function, big job" energy. sit down, grab a strawberry 🍓, let's go.

🎀 NAME 🎀

xe_guc_engine_activity_active_ticks — get engine active ticks ⏱️✨

🌸 SYNOPSIS 🌸

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

like, that's the whole signature. she's a u64, she takes three things, and she's literally iconic for it 💅

🦋 ARGUMENTS 🦋

  • guc — the GuC object 👑 your main character.
  • hwe — the hw_engine object 🔥 the engine we're snooping on.
  • fn_id — function id to report on 🌈 yes, that function. that one. the id says which.

💜 RETURN 💜

accumulated ticks hwe was active since engine activity stats were enabled 👏 not gonna lie, this is the good part: it's the accumulated ticks — meaning all the ticks piled up from the moment engine activity stats got switched on, up to now. no cap. ⭐

just a heads up bestie: it's since stats were enabled, not since forever 🙈 if you enabled them five minutes ago, you're getting five minutes' worth of ticks. periodt.

🧚 SEE ALSO 🧚

the whole friend group fr fr, they all show up together 😭🫶

and that's the page!! huge shoutout to ./drivers/gpu/drm/xe for housing all this, dated October 2026 — future vibes only 💀✨ mwah, go read the other ones too, slay 💅🎀

📦 where this page comes from