STRUCT ENGINE_ACTIVITY(9)

🌸 NAME 🌸

okay so this is the struct engine_activity manpage from the Kernel API Manual — it's literally the struct that holds engine specific activity data, iykyk 💅

---

✨ SYNOPSIS ✨

struct engine_activity {
    u64 active;
    u64 last_cpu_ts;
    u64 quanta;
    u64 quanta_ns;
    u64 quanta_remainder_ns;
    u64 total;
    bool running;
    struct guc_engine_activity_metadata metadata;
    struct guc_engine_activity activity;
 };

no cap, that's the whole shape of it 🫶

---

💅 MEMBERS 💅

okay bestie, member by member, let's go 🎀

• active — the current activity, like right now, in this exact moment ✨
• last_cpu_ts — the cpu timestamp in nsec of the previous sample — yes, nsec, nanoseconds, she's precise 💅
• quanta — total quanta used on HW 🔥
• quanta_ns — total quanta_ns used on HW 🔥
• quanta_remainder_ns — the remainder when the CPU time is scaled as per the quanta_ratio. and bestie listen, this remainder gets used in subsequent quanta calculations — she's not just leftover, she's load-bearing 😭
• total — total engine activity, the whole vibe check 👑
• running — true if engine is running some work, like when she's actually doing something 💀
• metadata — a snapshot of engine activity metadata 📸
• activity — a snapshot of engine activity counter 📸

---

🦋 DESCRIPTION 🦋

so basically this struct contains engine specific activity data plus a snapshot of the structures from GuC 🌈 that's it, that's the whole personality 🧚

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/gpu/drm/xe/xe_guc_engine_activity_types.h
• struct engine_activity_group(9)
• struct engine_activity_buffer(9)
• struct xe_guc_engine_activity(9)

go read those next, bestie, they're iconic ⭐

---

lowkey a whole moment. this one lives in ./drivers/gpu/drm/xe, dated October 2026, and the page name is struct engine_activity(9) — slay 💖🦋✨