xe_gt_sriov_pf_assert_vfid(9)
β¨ NAME β¨
xe_gt_sriov_pf_assert_vfid β okay so this one warns you if &id is not a supported VF number, but only when you're debugging π
πΈ SYNOPSIS πΈ
xe_gt_sriov_pf_assert_vfid (gt , vfid );
π ARGUMENTS π
gtβ the PFxe_gtyou wanna assert on, bestie π«Άvfidβ the VF number to assert, like, the actual number okurrr
π DESCRIPTION π
So what this does is assert that gt belongs to the Physical Function (PF) device, and that the vfid you handed it is within the range of supported VF numbers β up to the maximum number of VFs the driver can support, including VF0 which represents the PF itself β¨
It's giving "trust but verify" energy. Lowkey iconic π
π¦ NOTE π¦
This is effective only on debug builds, no cap. See Xe Asserts_ for more information π₯
π SEE ALSO π
Kernel file ./drivers/gpu/drm/xe/xe_gt_sriov_pf_helpers.h π§
And that's the whole vibe check π this page lives in ./drivers/gpu/drm/xe, stamped October 2026, and it's literally called xe_gt_sriov_pf_assert_vfid(9) β slay, go assert something bestie π
π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms