xe_gt_sriov...ority_locked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_gt_sriov...ority_locked(9) β€” bestie edition

okay so this is from the Kernel API Manual, and the function's full government name is xe_gt_sriov_pf_config_force_sched_priority_locked (the header up top just abbreviates it because even the manpage was like "girl that's long"). sit down, hydrate, let's go πŸ“


✨ NAME ✨

xe_gt_sriov_pf_config_force_sched_priority_locked β€” force update scheduling priority. that's it. that's the whole vibe. it forces, it updates, it's about priority, and yes it's locked (the name says so, respect it) πŸ‘‘


🌸 SYNOPSIS 🌸

void xe_gt_sriov_pf_config_force_sched_priority_locked (struct xe_gt *gt
, u32 priority );

returns void btw β€” so like, no return value, it just Does The Thing and leaves. main character energy fr fr ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • gt β€” the xe_gt. the gt in question. your gt. handle with care 🫢
  • priority β€” the new scheduling priority to set. brand new value, who dis πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea β˜• β€” this function lets you update the cached values of the scheduling priorities of all the VFs and the PF too, and it happens as a result of applying the GUC_KLV_VGT_POLICY_SCHED_IF_IDLE_ policy. every single one of them gets the glow-up, no VF left behind πŸ’–

⚠️ and listen β€” this function can only be called on PF. not VF. PF. that's the rule, that's the boundary, do not test it 😭

πŸ”₯ SEE ALSO πŸ”₯

first up, the literal source, the mothership:

  • Kernel file ./drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c

and now the whole friend group, the entire group chat, everyone's invited πŸŽ‰:


and that's the whole page bestie, you ate that πŸ’…βœ¨

sign-off time 🎬 β€” this little icon lives in ./drivers/gpu/drm/xe, it's dated October 2026, and it goes by xe_gt_sriov...ority_locked(9). mwah, go read the source, ily πŸ«ΆπŸ’–

πŸ“¦ where this page comes from