xe_guc_relay_process_guc2vf(9)
π xe_guc_relay_process_guc2vf(9) π
okay so bestie, welcome to the xe_guc_relay_process_guc2vf page β it's a kernel API manual entry, and yes it lives in the xe world, we love that for us β¨
πΈ NAME πΈ
xe_guc_relay_process_guc2vf β literally the function that handles a relay notification message from the GuC. that's it, that's the whole vibe π
β¨ SYNOPSIS β¨
int xe_guc_relay_process_guc2vf (struct xe_guc_relay *relay , const u32 *msg , u32 len );
like, look at her signature. so iconic. π
π¦ ARGUMENTS π¦
relayβ thexe_guc_relaywhich will handle the message π she's the main character here, she does the handlingmsgβ the message to be handled, okurrr π«Άlenβ the length of the message, and bestie it is measured in dwords (do not forget the dwords, i'm serious π)
π DESCRIPTION π
so what does she actually do? this function will handle relay messages received from the GuC. that's the whole job. she receives, she handles, she slays. π₯
β οΈ important vibe check: this function can only be used if the driver is running in SR-IOV mode. no SR-IOV, no function. periodt. π
β RETURN β
0on success π- a negative error code on failure π
that's it. clean. simple. we stan a straightforward return value ngl.
π§ SEE ALSO π§
- Kernel file
./drivers/gpu/drm/xe/xe_guc_relay.cπ 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_guc2pf(9)
go read those too, they're all connected, iykyk π
aaaand that's the page!! πΈ the source/version line says this beauty comes from ./drivers/gpu/drm/xe, dated October 2026, and the manual page is xe_guc_relay_process_guc2vf(9) β okay love you bye, go handle those messages responsibly π«Άβ¨π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms