xe_gt_sriov_..._lmem_locked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

xe_gt_sriov_..._lmem_locked(9) πŸ’…

okay so bestie, you opened the Kernel API Manual and landed on xe_gt_sriov_..._lmem_locked(9). The full-name reveal is xe_gt_sriov_pf_config_bulk_set_lmem_locked, and she is here to provision many VFs with LMEM. iconic behavior, honestly.


✨ NAME ✨

xe_gt_sriov_pf_config_bulk_set_lmem_locked β€” Provision many VFs with LMEM. no cap.


πŸ”₯ SYNOPSIS πŸ”₯

int xe_gt_sriov_pf_config_bulk_set_lmem_locked (struct xe_gt *gt ,
       unsigned int vfid , unsigned int num_vfs , u64 size );

πŸŽ€ ARGUMENTS πŸŽ€

  • gt β€” the xe_gt β€” and nope, it can't be media.
  • vfid β€” starting VF identifier β€” and 0 is a no-go.
  • num_vfs β€” number of VFs to provision.
  • size β€” requested LMEM size.

πŸ’… DESCRIPTION πŸ’…

This function can only be called on PF. that's the whole vibe check.


🌈 RETURN 🌈

0 on success, or a negative error code on failure. periodt.


πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c β€” go look, iykyk.

the whole squad:


mwah πŸ’‹ and for the footer bestie: source/version is ./drivers/gpu/drm/xe, the date is October 2026, and the manual tag is xe_gt_sriov_..._lmem_locked(9). cute little sign-off instead of copy-pasting the line. 🫢

πŸ“¦ where this page comes from