xe_guc_ct_send_recv(9)

💅 xe_guc_ct_send_recv(9) 💅

okay so bestie, welcome to the Kernel API Manual ✨ — this page is literally about sending and receiving HXG to the GuC, and it's lowkey iconic. Let's get into it 🫶

🎀 NAME 🎀

xe_guc_ct_send_recv — send and receive HXG to the GuC 💌

✨ SYNOPSIS ✨

Here's the exact signature, no cap:

int xe_guc_ct_send_recv (struct xe_guc_ct *ct , const u32 *action , u32
       len , u32 *response_buffer );

🧚 ARGUMENTS 🧚

• ct — the xe_guc_ct 💖
• action — the dword array with HXG Request_ message (can't be NULL) 🚫
• len — length of the HXG Request_ message (in dwords, can't be 0) 🔢
• response_buffer — placeholder for the HXG Response_ message (can be NULL) 🌸

🦋 DESCRIPTION 🦋

So like, this sends a HXG Request_ message to the GuC over the CT communication channel, then blocks until the GuC replies with a HXG Response_ message. It's giving "wait for it" energy 😭✨

For non-blocking communication with GuC, use xe_guc_ct_send — that's the main character who doesn't wait 💅

💀 NOTE 💀

bestie, listen: the size of response_buffer must be at least GUC_CTB_MAX_DWORDS_. That's not a suggestion, that's the rule 🫶

🌈 RETURN 🌈

It returns the response length (in dwords) if response_buffer was not NULL, or DATA0 from HXG Response_ if response_buffer was NULL, or a negative error code on failure. Periodt 💅

👑 SEE ALSO 👑

• Kernel file ./drivers/gpu/drm/xe/xe_guc_ct.c
• GuC CTB Blob(9)
• xe_guc_ct_queue_proc_time_jiffies(9)
• xe_guc_ct_init_post_hwconfig(9)
• xe_guc_ct_restart(9)
• xe_guc_ct_enable(9)
• xe_guc_ct_disable(9)
• xe_guc_ct_flush_and_stop(9)
• xe_guc_ct_stop(9)
• xe_guc_ct_runtime_suspend(9)
• xe_guc_ct_runtime_resume(9)
• xe_guc_ct_send(9)
• xe_guc_ct_fast_path(9)
• xe_guc_ct_snapshot_capture(9)
• xe_guc_ct_snapshot_print(9)
• xe_guc_ct_snapshot_free(9)
• xe_guc_ct_print(9)

---

okay bye bestie! source/version: ./drivers/gpu/drm/xe, dated October 2026, all about xe_guc_ct_send_recv(9) — mwah 💋💖