xe_guc_relay_process_guc2pf(9)

💅 xe_guc_relay_process_guc2pf 💅

okay bestie, so this is a page from the Kernel API Manual and it's literally all about xe_guc_relay_process_guc2pf — say that five times fast, i dare you 🫶

---

✨ NAME ✨

xe_guc_relay_process_guc2pf — handle relay notification message from the GuC. that's it, that's the whole vibe 💖

---

🌸 SYNOPSIS 🌸

int xe_guc_relay_process_guc2pf (struct xe_guc_relay *relay , const u32 *msg , u32 len );

like, it takes three things and gives you back an int, no cap ✨

---

🎀 ARGUMENTS 🎀

• relay — the xe_guc_relay which will handle the message. this is the main character doing the handling, periodt 👑
• msg — message to be handled. the actual message, right there, ready for its moment 🦋
• len — length of the message (in dwords). yes bb, dwords, not bytes, don't come for me 🙈

---

💜 DESCRIPTION 💜

so this function will handle relay messages received from the GuC. like, GuC sends something over, this is the one that deals with it. lowkey iconic 🔥

but here's the thing, bestie — and this is important so listen up: this function can only be used if driver is running in SR-IOV PF mode. that's the vibe check. if you're not in SR-IOV PF mode, this is not the function for you, fr fr 😭

---

⭐ RETURN ⭐

0 on success or a negative error code on failure. slay when it's zero, sad girl hours when it's negative 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/xe/xe_guc_relay.c — the whole source file, go read it, iykyk 📖
• struct relay_transaction(9)
• xe_guc_relay_init(9)
• xe_guc_relay_send_to_vf(9)
• xe_guc_relay_send_to_pf(9)
• xe_guc_relay_process_guc2vf(9) — the sibling, the other half of the relay saga 🧚

---

aaaand that's the page!! this one's from ./drivers/gpu/drm/xe, dated October 2026, and it's filed under xe_guc_relay_process_guc2pf(9) — go off, you understood it perfectly, i'm so proud of you 💅💖🎀