xe_rtp_match_always(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ xe_rtp_match_always β€” Match RTP entry unconditionally ✨

okay bestie, welcome to the xe_rtp_match_always(9) page πŸ’… this one lives in the Kernel API Manual and honestly? it's the chillest little function in the whole RTP rule family. no cap.


🌸 NAME 🌸

xe_rtp_match_always β€” Match RTP entry unconditionally πŸ”₯

like, unconditionally. that's the whole personality. she matches. always. periodt.


πŸŽ€ SYNOPSIS πŸŽ€

bool xe_rtp_match_always (const struct xe_device *xe , const struct
       xe_gt *gt , const struct xe_hw_engine *hwe );

she takes three arguments, gives you back a bool, and she is NOT here to gatekeep 🫢


πŸ’– ARGUMENTS πŸ’–

  • xe β€” Device structure ✨ (yes, the whole device. she doesn't even look at it, but it's invited.)
  • gt β€” GT structure πŸ’œ (also invited. also not looked at.)
  • hwe β€” Engine instance 🌈 (you guessed it β€” invited, not looked at.)

ngl the way this function takes three whole arguments and then does absolutely nothing with them is such main character energy 😭


⭐ RETURN ⭐

true, regardless of inputs πŸ‘‘

literally. regardless. doesn't matter what you pass, doesn't matter what mood the hardware is in β€” she's returning true. icon behavior, honestly.


πŸ¦‹ SEE ALSO πŸ¦‹

y'all want the rest of the squad? they're all in the kernel file ./drivers/gpu/drm/xe/xe_rtp.h and here's the full lineup, no skips:

every single one, bestie. iykyk πŸ’€


heads up: all those rules and actions are buddies of this one, but this one is the one that never says no πŸ™ˆ if you need actual conditional logic, go bother one of the others β€” xe_rtp_match_always is just here to vibe.

okay that's the whole page, you ate that πŸ“ and before you go β€” this little gem comes from ./drivers/gpu/drm/xe, dated October 2026, manual page xe_rtp_match_always(9). mwah, go touch some hardware πŸ’‹πŸ§š

πŸ“¦ where this page comes from