xe_rtp_rule_matches(9)

✨ NAME ✨

xe_rtp_rule_matches — bestie, this is the little function that checks whether a whole set of RTP rules matches against the device / GT / hwe 💅 like a vibe check but for hardware

(and yes it's a kernel API manual page, we're being fancy today 👑)

---

🌸 SYNOPSIS 🌸

bool xe_rtp_rule_matches (const struct xe_device *xe , struct xe_gt *gt
, struct xe_hw_engine *hwe , const struct xe_rtp_rule *rules , unsigned
int n_rules , int *err );

okay so it's bool in, bool out, and the only way you get a true is if everything lines up ✨ no cap

---

🎀 ARGUMENTS 🎀

• xe — the xe device 🖥️ literally the star of the show, main character energy
• gt — the GT struct (may be NULL, so it's giving 'optional bestie' 🫶)
• hwe — the hw_engine (also may be NULL, love that for us 🙈)
• rules — the array of rules to match against, this is the whole shopping list 🛍️
• n_rules — number of items in rules, don't forget to count fr fr 🔢
• err — pointer (may be NULL, we do love a flexible icon 💅) that gets set with the error number

---

💖 DESCRIPTION 💖

so what it does is: it parses the set of rules and checks if they match against the parameters you passed in 🔥 like a matching game but make it kernel

if the call passes, err gets updated with a non-zero negative error number, or zero if no errors were found during the parsing/evaluation of rules 👀 — so like, 0 = we're so back, negative = it's over 😭

⚠️ heads up bestie: it returns true if there is a match, and false if there is no match or if an error was found. yes, "no match" and "something went wrong" both come back as false — that's why err is right there, use it!! 💀

---

🦋 SEE ALSO 🦋

• Kernel file ./drivers/gpu/drm/xe/tests/xe_rtp.c — go read it, iykyk 📖✨

---

aaaaaaaaand that's the page 🎀 this was brought to you by the Kernel API Manual, living in ./drivers/gpu/drm/xe/tests, dated October 2026 — stay slay, stay matched, periodt 💜🌈⭐