xe_sriov_pf...pply_vf_vram(9)

📦 version 7.3.1, in nixpkgs unstable

💅 xe_sriov_pf_provision_apply_vf_vram 💅

okay so bestie, we're in the Kernel API Manual, section 9, and this page is literally about changing one single VF's VRAM allocation. one. single. VF. the audacity, the precision, the focus ✨

🎀 NAME 🎀

xe_sriov_pf_provision_apply_vf_vram — Change single VF VRAM allocation.

like, one VF. just the one. not all of them. a single one. 🫶

⭐ SYNOPSIS ⭐

int xe_sriov_pf_provision_apply_vf_vram (struct xe_device *xe , unsigned
       int vfid , u64 size );

the way that this function takes exactly three things and returns an int… no cap, that's main character energy 💜

🌸 ARGUMENTS 🌸

  • xe — the PF xe_device. this is the parent, the group chat admin, the one holding it all together 👑
  • vfid — the VF identifier. and heads up bestie: it can't be 0 == PFID. zero is the PF's own seat, it's taken, do not sit there 🙈
  • size — the VRAM size to set. this is the number you're assigning, the whole point of the operation, periodt 🍓

💖 DESCRIPTION 💖

Change the VF's VRAM provisioning on all tiles/GTs. all of them. every tile, every GT, no tile left behind, we love an even distribution 💅

⚠️ real talk: this function can only be called on PF. it's PF-only, that's the vibe check, don't come at it from a VF and expect it to slay 😭

🔥 RETURN 🔥

0 on success, or a negative error code on failure. that's it, that's the whole story — zero means we ate, negative means something went sideways 💀

🦋 SEE ALSO 🦋

kernel file ./drivers/gpu/drm/xe/xe_sriov_pf_provision.c — the source, the origin, the home base 🎀

and the whole friend group, because this function does not travel alone:

like a full roster. bulk apply, single apply, query — the whole trio for eq, pt, priority and vram. iykyk 🌈

alright bestie, that's the whole page 💖 this one lives in ./drivers/gpu/drm/xe, it's from the Kernel API Manual, dated October 2026 — go forth and provision responsibly, mwah 🧚 💜

📦 where this page comes from