xe_guc_id_mg...serve_locked(9)

📦 version 7.3.1, in nixpkgs unstable

💖 xe_guc_id_mg...serve_locked(9) 💖

okay so this is a page from the Kernel API Manual and honestly? she's niche but she's iconic. buckle up bestie, we're getting you a GuC context ID ✨

🌸 NAME 🌸

xe_guc_id_mgr_reserve_locked — reserve one or more GuC context IDs 💅

🎀 SYNOPSIS 🎀

int xe_guc_id_mgr_reserve_locked (struct xe_guc_id_mgr *idm , unsigned
       int count );

like literally that's the whole call, that's the vibe 🦋

⭐ ARGUMENTS ⭐

  • idm — the xe_guc_id_mgr, aka the manager struct in question. she's the main character here 👑
  • count — how many IDs you want to allocate. warning bestie: this can't be 0 — zero is not the move, don't do it 🙈

💜 DESCRIPTION 💜

okay so this function is dedicated for the use by the GuC submission code, where the submission lock is already taken. that's the whole point of the _locked in her name, iykyk 🔥

fr fr if you're not in that code path, this is not your function — she's spoken for 💀

🌈 RETURN 🌈

  • the ID of the allocated GuC context if everything slays ✨
  • or a negative error code on failure 😭 (ngl, if you see a negative, something went sideways)

🦋 SEE ALSO 🦋

Kernel file ./drivers/gpu/drm/xe/xe_guc_id_mgr.c — go read the source, it's giving transparency 🫶

like the whole friend group, honestly 💖

mwah 💋 this page lives in ./drivers/gpu/drm/xe, says October 2026, and answers to the name xe_guc_id_mg...serve_locked(9) — periodt, that's the whole manpage, love u bye 🎀💜

📦 where this page comes from