XE_RTP_ACTION_FLAG(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… XE_RTP_ACTION_FLAG πŸ’…

okay bestie, welcome to the Kernel API Manual page for XE_RTP_ACTION_FLAG β€” she's a helper macro and she's lowkey iconic ✨

🌸 NAME 🌸

XE_RTP_ACTION_FLAG β€” the helper that adds a whole bunch of flags to a struct xe_rtp_action for you 🫢

✨ SYNOPSIS ✨

XE_RTP_ACTION_FLAG (... );

πŸŽ€ ARGUMENTS πŸŽ€

  • ... β€” the action flags themselves, but pls notice: you pass them without the XE_RTP_ACTION_FLAG_ prefix, because the macro is gonna add that for you πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

so basically, this macro is your bestie that automatically slaps a XE_RTP_ACTION_FLAG_ prefix onto the flags whenever you're defining struct xe_rtp_action entries. no cap, it just does the tedious part for you so you don't have to type the whole long name every single time 😭

here's the example, verbatim, because it ate:

const struct xe_rtp_entry_sr wa_entries[] = {
        ...
        { XE_RTP_NAME("test-entry"),
          ...
          XE_RTP_ACTION_SET(..., XE_RTP_ACTION_FLAG(FOREACH_ENGINE)),
          ...
        },
        ...
};

see how FOREACH_ENGINE just goes in raw and the prefix appears like magic? that's the vibe check passing πŸ”₯

🌈 SEE ALSO 🌈


that's the whole page bestie, go forth and flag responsibly πŸ‘‘

source: ./drivers/gpu/drm/xe Β· October 2026 Β· XE_RTP_ACTION_FLAG(9) β€” mwah, bye πŸ’‹πŸŽ€

πŸ“¦ where this page comes from