STRUCT XE_SYSCTRL_EVENT_RESPONSE(9)
๐ธ 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 au32.eventโ the pending event type. Au32that tells you which kind of event we're talking about ๐timestampโ timestamp of the most recent event. It's au64, so she's got range ๐extendedโ au32bitfield of1bit: this says the event has an extended payload. Yup, just the one bit, she's lowkey minimal ๐ธreservedโ au32bitfield of31bits, 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.henum 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
- nixpkgs unstable: linux-manual 7.3.1
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms