xe_gt_sriov...ocess_guc2pf(9)
π xe_gt_sriov_pf_monitor_process_guc2pf β NAME β¨
okay so bestie, this is xe_gt_sriov_pf_monitor_process_guc2pf β the one that handles adverse event notification from the GuC π«Ά like, that's literally its whole job. no cap. it's from the Kernel API Manual and it lives in ./drivers/gpu/drm/xe, iykyk.
πΈ SYNOPSIS πΈ
int xe_gt_sriov_pf_monitor_process_guc2pf (struct xe_gt *gt , const u32 *msg , u32 len );
look at her. iconic signature. returns an int, takes three little args. periodt π
π ARGUMENTS π
gtβ thexe_gtπ¦ like, the GT in question, she's the main character heremsgβ the G2H event message β (GuC-to-Host, so it's the GuC sliding into your inbox fr fr)lenβ length of the message, because we gotta know how much message there is π
π₯ DESCRIPTION π₯
so what does she actually do? she handles adverse event notification from the GuC. that's the vibe check she's running.
real talk tho: this function is intended for PF only π not VF, not anybody else. PF. that's the whole circle. don't be out here calling her from the wrong context, bestie π
β¨ RETURN β¨
0β success, we ate, everybody's happy π- negative error code β failure, oh no, it's giving tragedy π
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/xe/xe_gt_sriov_pf_monitor.cβ go read the source, it's right there, no excuses π xe_gt_sriov_pf_monitor_flr(9)β her bestiexe_gt_sriov_pf_monitor_print_events(9)β her other bestie, the one who prints the events π§
and that's the page, bestie!! shipped with love from ./drivers/gpu/drm/xe, dated October 2026, out of the Kernel API Manual β mwah, go handle those adverse events 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