xe_sriov_pf...ply_priority(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_sriov_pf_provision_bulk_apply_priority β€” the Kernel API Manual, bestie edition ✨

okay so bestie, welcome to the Kernel API Manual entry for xe_sriov_pf_provision_bulk_apply_priority(9) β€” yes the name is a whole mouthful, the header literally truncates it to xe_sriov_pf...ply_priority(9) because even the manpage was like "girl, abbreviate" 😭. Anyway. She's iconic, she's a function, and she's about to change the scheduling priority of everyone: all the VFs and the PF at once. main character energy fr fr πŸ‘‘


🌸 NAME 🌸

xe_sriov_pf_provision_bulk_apply_priority β€” changes the scheduling priority of all VFs and the PF. that's her whole job, no cap πŸ’…


✨ SYNOPSIS ✨

int xe_sriov_pf_provision_bulk_apply_priority(struct xe_device *xe,
                                              u32 prio);

πŸ¦‹ ARGUMENTS πŸ¦‹

  • xe β€” the PF xe_device. yes the PF one, we'll get to why that matters in a sec πŸ™ˆ
  • prio β€” the scheduling priority you wanna set. that's the number going in, bestie πŸŽ€

πŸ’– DESCRIPTION πŸ’–

So like β€” this function changes the scheduling priority provisioning on all tiles/GTs. all of them. the whole squad. no VF left behind 🫢

⚠️ real talk though: this function can only be called on the PF. that's not a vibe suggestion, that's the rule. don't come at her from a VF, she will simply not have it πŸ’€

πŸ”₯ RETURN πŸ”₯

  • 0 on success β€” slay ✨
  • a negative error code on failure β€” not slay, but at least you know 😭

⭐ SEE ALSO ⭐

the friend group, in order, don't lose anyone:

iykyk πŸ‘€ that's the entire provision lore, go read them all, she said so 🌈


and that's the page, bestie πŸŽ€ this lil gem lives over in ./drivers/gpu/drm/xe and it's dated October 2026 β€” so like, future her, living her best life ⭐ periodt πŸ’œ 🧚

πŸ“¦ where this page comes from