xe_guc_submit_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_guc_submit_init(9)

okay so this is a page from the Kernel API Manual (that's the manual name, bestie, consider it folded in 🫢) and it's all about one tiny little function that gets GuC submission up and running. It's giving "setup era" and honestly? iconic.


✨ NAME ✨

xe_guc_submit_init β€” Initialize GuC submission.

That's it. That's the whole job. She initializes. She submits. She slays.


🌸 SYNOPSIS 🌸

int xe_guc_submit_init (struct xe_guc *guc , unsigned int num_ids );

πŸŽ€ ARGUMENTS πŸŽ€

  • guc β€” the xe_guc you wanna initialize. Like, the actual thing getting set up. Your main character struct πŸ’–
  • num_ids β€” number of GuC context IDs to use. How many IDs we giving her? You decide, bestie.

πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the vibe check πŸ‘‘: the bare-metal driver or the PF driver can pass ~0 as num_ids to say "hey, just use all the GuC context IDs that the GuC firmware supports for submission." No cap, that's the flex β€” let the firmware tell you what's available and take the whole buffet.

Only VF drivers have to actually sit down and provide an explicit number of GuC context IDs that they can use for submission. Like, VF drivers don't get the "surprise me" option, they gotta do the math themselves πŸ™ˆ.


⭐ RETURN ⭐

0 on success, or a negative error code on failure. That's the whole report card β€” zero means she ate, negative means something went sideways 😭


🌈 SEE ALSO 🌈


ok that's the whole page, go read the source file if you want the lore, iykyk πŸ’€

and that's a wrap, bestie πŸ§šπŸ’œ this came out of ./drivers/gpu/drm/xe, dated October 2026, and it's literally just xe_guc_submit_init(9) living her best life in the Kernel API Manual. periodt. πŸ“πŸ”₯

πŸ“¦ where this page comes from