xe_gt_sriov_...get_lmem_obj(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_gt_sriov_...get_lmem_obj β€” a Kernel API Manual moment ✨

okay so bestie, welcome to the (9) page for xe_gt_sriov_...get_lmem_obj β€” she lives in the Kernel API Manual and honestly? she's lowkey iconic. let's get into it πŸŽ€


🌸 NAME 🌸

xe_gt_sriov_pf_config_get_lmem_obj β€” takes a reference to the struct xe_bo that's backing the VF LMEM. that's it, that's the whole vibe. grabbing a ref, being responsible about it, slaying 🫢


✨ SYNOPSIS ✨

struct xe_bo * xe_gt_sriov_pf_config_get_lmem_obj (struct xe_gt *gt ,
       unsigned int vfid );

like look at her go πŸ’–


πŸ¦‹ ARGUMENTS πŸ¦‹

  • gt β€” the xe_gt. your graphics tile, your whole situation.
  • vfid β€” the VF identifier. and listen πŸ‘ she can't be 0. zero is not invited to this party, fr fr.

πŸ‘‘ DESCRIPTION πŸ‘‘

the way this one's simple: this function can only be called on PF. not VF, PF. that's the rule, periodt.

and the caller β€” that's you, bestie β€” you are responsible for calling xe_bo_put on the object you get back. no cap, that's on you. hold the ref, then put the ref. balance. main character energy but make it memory management πŸ’€


🌈 RETURN 🌈

a pointer to the struct xe_bo backing VF LMEM (if any). if any 🫢


⭐ SEE ALSO ⭐

the whole friend group, and we're tagging everyone β€” iykyk:


🫢 reminder bestie: PF only, and xe_bo_put on the way out. don't leave her hanging πŸ’œ

and that's the page!! sign-off time: she's sourced from ./drivers/gpu/drm/xe, dated October 2026, and yes the header up top was xe_gt_sriov_...get_lmem_obj(9) because we keep the branding πŸ’…βœ¨ bye ily, go put your bo πŸŽ€

πŸ“¦ where this page comes from