xe_guc_id_mgr_reserve(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– xe_guc_id_mgr_reserve(9) πŸ’–

okay bestie, welcome to the Kernel API Manual entry for xe_guc_id_mgr_reserve(9) β€” yes that's a whole mouthful, but she's iconic and we're gonna get through it together 🫢


✨ NAME ✨

xe_guc_id_mgr_reserve β€” bestie, this one reserves a range of GuC context IDs. that's the whole vibe ✨


🌸 SYNOPSIS 🌸

int xe_guc_id_mgr_reserve (struct xe_guc_id_mgr *idm , unsigned int
       count , unsigned int retain );

like literally that's the signature, no notes πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • idm β€” the xe_guc_id_mgr in question. she's the main character here πŸ‘‘
  • count β€” how many GuC context IDs you wanna reserve. absolutely can't be 0 β€” zero is not the move, ok? 🚫
  • retain β€” how many GuC context IDs you gotta keep available. also can't be 0, no exceptions 😀

πŸ¦‹ DESCRIPTION πŸ¦‹

so this function is dedicated for use by the PF driver, and the PF driver has some strong opinions, ngl. it expects two things:

  1. the reserved range of IDs will be contiguous β€” no gaps, she stays together 🧚
  2. there will be at least retain IDs still available for the PF after this reservation β€” like you can't just take everything, leave some for later bestie 😭

⭐ RETURN ⭐

on success you get the starting ID of the allocated GuC context ID range β€” slay πŸ”₯

on failure? a negative error code. so if you see a negative number, that's your sign something went off, no cap πŸ’€


🌈 SEE ALSO 🌈


ngl the whole squad is linked up there, go read them too, iykyk πŸ’œ

and that's the page bestie!! this one came straight outta ./drivers/gpu/drm/xe, dated October 2026 β€” yes, the future, we're that ahead of the game πŸ‘‘βœ¨ mwah, ily, go reserve those IDs responsibly πŸ“πŸ’…

πŸ“¦ where this page comes from