xe_guc_ct_enable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_guc_ct_enable(9) β€” the Kernel API Manual page bestie πŸ’…

Okay so first things first, this is from the Kernel API Manual, and the whole entire page is about xe_guc_ct_enable β€” yes that's a lot of letters, we'll get through it together 🫢


✨ NAME ✨

xe_guc_ct_enable β€” literally just: Enable GuC CT. That's the whole vibe. Short, sweet, iconic πŸ‘‘


🌸 SYNOPSIS 🌸

int xe_guc_ct_enable (struct xe_guc_ct *ct );

That's it. One function, one argument, returns an int. Clean. Minimal. Main character energy fr fr.


πŸŽ€ ARGUMENTS πŸŽ€

  • ct β€” the xe_guc_ct. Yep. That's the description. It's a struct xe_guc_ct * and it's the thing you're enabling. No notes, no cap πŸ’€

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so what does this thing actually do? Two whole jobs, bestie:

  • It enables GuC CT, bringing it to an empty state 🧹
  • Then it issues a CT register MMIO command πŸ“‘

That's the tea. Empty state first, then the MMIO command gets issued. Slay ✨


⭐ RETURN ⭐

  • 0 β€” success, we ate πŸ“
  • a negative errno β€” on failure 😭 check that errno value, it's telling you something

πŸ‘‘ SEE ALSO πŸ‘‘

Everything's here in ./drivers/gpu/drm/xe/xe_guc_ct.c β€” the source file, the mothership, the blueprint πŸ’œ And also all these sibling functions, go say hi to them:

Like, look at that family tree. Gorgeous 🌈

One (1) tiny thing: the manpage source line here literally wraps Kernel file ./drivers/gpu/drm/xe/xe_guc_ct.c onto the list right before GuC CTB Blob(9), so that's exactly how we're rolling with it πŸ’–

Okay that's the page!! Signing off from ./drivers/gpu/drm/xe, this is the October 2026 edition of the Kernel API Manual β€” stay hydrated, read your errno values, and remember: a negative return is not a personality flaw, it's data πŸ§šπŸ’œ

πŸ“¦ where this page comes from