XE_RTP_ACTIONS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… XE_RTP_ACTIONS πŸ’…

okay bestie, real talk: this is a kernel API manual page (XE_RTP_ACTIONS(9)) from the Linux Kernel API Manual, and it's genuinely one of the cutest little helpers in ./drivers/gpu/drm/xe. let's get into it πŸŽ€


✨ NAME ✨

XE_RTP_ACTIONS β€” a helper that sets multiple actions onto a struct xe_rtp_entry_sr. that's it. that's the whole job. and it eats every time 🫢


🌸 SYNOPSIS 🌸

XE_RTP_ACTIONS (... );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • ... β€” the actions to be taken. literally just feed it your actions, bestie πŸ’…

πŸ‘‘ DESCRIPTION πŸ‘‘

so here's the vibe check: you need at least one action. can't show up to the function with zero actions, that's not the move. πŸ™ˆ

and the ceiling? you can pass up to 12 actions. twelve! iconic capacity, no cap. πŸ”₯

wanna know what actions are even allowed? go peek at XE_RTP_ACTION_* β€” that's where all the possible actions live, iykyk.

here's an example of the whole thing in the wild, and yes it's giving main character energy:

const struct xe_rtp_entry_sr wa_entries[] = {
        ...
        { XE_RTP_NAME("test-entry"),
          XE_RTP_RULES(...),
          XE_RTP_ACTIONS(SET(..), SET(...), CLR(...)),
          ...
        },
        ...
};

see how XE_RTP_ACTIONS(...) is just sitting there stacking SET(..), SET(...) and CLR(...) together? that's the moment. periodt. ✨


🌈 SEE ALSO 🌈

bestie there is SO much lore here, go read all of it, i'm obsessed:


ngl bestie, that's a LOT of see-alsos. drink some water, stretch, then come back and read them all. hydration is self care πŸ’–πŸ§š

and that's the whole page, mwah πŸ’‹ β€” this cutie came straight from ./drivers/gpu/drm/xe, dated October 2026. go forth and stack your actions (one to twelve of them, remember πŸ‘), and slay πŸ’…βœ¨πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from