STRUCT XE_SYSCTRL_EVENT_RESPONSE(9)

๐Ÿ“ฆ version 7.3.1, in nixpkgs unstable

๐ŸŒธ NAME ๐ŸŒธ

struct xe_sysctrl_event_response โ€” the response struct for a pending event, bestie. It's giving โœจ"here's what's up with your events"โœจ energy, and it lives in the Kernel API Manual (that's the manual name, clocked it for you ๐Ÿซถ).


โœจ SYNOPSIS โœจ

struct xe_sysctrl_event_response {
    u32 count;
    u32 event;
    u64 timestamp;
    u32 extended:1;
    u32 reserved:31;
    u32 data[XE_SYSCTRL_EVENT_DATA_LEN];
 };

Like, that's the whole shape of it. Six little fields, all main character energy ๐Ÿ’…


๐ŸŽ€ Members ๐ŸŽ€

Okay so let's meet the cast, one by one, no skips:

  • count โ€” the pending event count after this response. So like, how many events are still waiting around being dramatic ๐Ÿ˜ญ it's a u32.
  • event โ€” the pending event type. A u32 that tells you which kind of event we're talking about ๐Ÿ‘‘
  • timestamp โ€” timestamp of the most recent event. It's a u64, so she's got range ๐Ÿ’–
  • extended โ€” a u32 bitfield of 1 bit: this says the event has an extended payload. Yup, just the one bit, she's lowkey minimal ๐ŸŒธ
  • reserved โ€” a u32 bitfield of 31 bits, reserved for future use. Not for you, not for me, for the future ๐Ÿ”ฎ literally do not touch.
  • data โ€” the generic event data. It's an array: u32 data[XE_SYSCTRL_EVENT_DATA_LEN]; โ€” the length lives in that macro, iykyk ๐Ÿฆ‹
Fr fr: reserved is reserved for future use, so don't be out here assigning to it like it's yours. It is not yours. Respect the reserve ๐Ÿ™ˆ

๐Ÿ’œ SEE ALSO ๐Ÿ’œ

  • Kernel file ./drivers/gpu/drm/xe/xe_sysctrl_event_types.h enum
  • xe_sysctrl_event(9)
  • struct xe_sysctrl_event_request(9)

Go read those next, they're the friend group this struct rolls with ๐Ÿซถ


That's the whole vibe check, bestie โ€” you ate it up โœจ This lil' page lives at ./drivers/gpu/drm/xe, and the version/date stamp on it is October 2026 ๐Ÿ“๐Ÿ’ซ Slay, go forth and read your events ๐Ÿ’…๐Ÿ‘‘

๐Ÿ“ฆ where this page comes from