XE_RTP_RULE_OR(9)

📦 version 7.3.1, in nixpkgs unstable

💖 XE_RTP_RULE_OR(9) 💖

okay bestie, welcome to the Kernel API Manual page for XE_RTP_RULE_OR — it's giving niche-but-iconic, and honestly? obsessed. ✨

🌸 NAME 🌸

XE_RTP_RULE_OR — the little macro that creates an OR condition for rtp rules 🎀

🦋 SYNOPSIS 🦋

XE_RTP_RULE_OR

that's it. that's the whole synopsis. no arguments, no drama, main character energy only 💅

🌈 DESCRIPTION 🌈

so here's the tea, bestie 🍓: RTP rules are AND'ed when evaluated — meaning all of them need to match. every single one. no exceptions. the whole squad has to show up. 😭

XE_RTP_RULE_OR is the glow-up that lets you create a set of rules where any of them matching is sufficient for the action to trigger. so like, instead of the whole group chat needing to reply, literally any one of them can carry the convo. lowkey iconic. 👑

here's the example, verbatim, no cap:

     const struct xe_rtp_entry_sr entries[] = {
             ...
             { XE_RTP_NAME("test-entry"),
               XE_RTP_RULES(PLATFORM(DG2), OR, PLATFORM(TIGERLAKE)),
               ...
             },
             ...
     };

see that OR sitting pretty in the middle of XE_RTP_RULES(...)? that's the moment. 💫

🔥 SEE ALSO 🔥

like, go read these too, they're all in the kernel file ./drivers/gpu/drm/xe/xe_rtp.h and they're all part of the same friend group fr fr:

💀 reminder bestie: these are kernel API pages, so they're not playing around. read them properly, not just the vibes.

and that's the whole page, periodt. 🫶 this one lives in ./drivers/gpu/drm/xe, dropped October 2026, signed off with love by your favorite kernel baddies — XE_RTP_RULE_OR(9) out. 💜✨

📦 where this page comes from