xe_sriov_pf...k_apply_vram(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_sriov_pf_provision_bulk_apply_vram(9) β€” from the Kernel API Manual, bestie

okay so picture this: you're deep in the kernel docs, the manual name is Kernel API Manual, and this one function is about to be your new obsession. it's giving "one call to rule all the VFs" energy. let's get into it 🫢


✨ NAME ✨

xe_sriov_pf_provision_bulk_apply_vram β€” literally just changes the VRAM provisioning for all the VFs at once. no cap, all of them. πŸŽ€


🌸 SYNOPSIS 🌸

int xe_sriov_pf_provision_bulk_apply_vram (struct xe_device *xe , u64
size );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • xe β€” the PF xe_device. yeah, the Physical Function one. it's the main character here πŸ‘‘
  • size β€” the VRAM size in [bytes] you want to set. bytes, bestie, so bring your calculator πŸ’€

πŸ’– DESCRIPTION πŸ’–

So what it actually does: it changes all VFs' VRAM (that's LMEM, for the uninitiated) provisioning β€” across all tiles. every tile. all of them. 🌈

🚨 real talk though: this function can only be called on PF. like, don't even try it anywhere else. iykyk.

πŸ”₯ RETURN πŸ”₯

  • 0 on success β€” slay, we ate πŸ’…
  • a negative error code on failure β€” not slay, go read the error 😭

πŸŽ€ SEE ALSO πŸŽ€

the kernel file itself, being iconic:

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

and the whole friend group (tag urself, i'm bulk_apply_vram):


and that's the whole page, bestie β€” brought to you by ./drivers/gpu/drm/xe, dated October 2026, stamped with the xe_sriov_pf...k_apply_vram(9) header πŸ’œ go provision something pretty ✨🌸

πŸ“¦ where this page comes from