xe_sriov_pf..._query_vf_pt(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_sriov_pf..._query_vf_pt(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual ✨ β€” we're talking about xe_sriov_pf_provision_query_vf_pt, and the whole vibe is β€œPF, please go ask the provisioning bits what the VF’s preemption timeout is.” No cap. 🫢


🌸 NAME 🌸

xe_sriov_pf_provision_query_vf_pt β€” Query VF's preemption timeout. πŸ’–


✨ SYNOPSIS ✨

       int xe_sriov_pf_provision_query_vf_pt (struct xe_device *xe , unsigned
       int vfid , u32 *pt );

🫢 ARGUMENTS 🫢

  • xe β€” the PF xe_device, bestie. That's the device arg, and it’s giving PF main character energy. πŸ’œ
  • vfid β€” the VF identifier. Which VF are we talking about? This one. πŸŽ€
  • pt β€” placeholder for the returned preemption timeout in [us]. It’s literally where the returned value goes, ngl. πŸ™ˆ

πŸ’– DESCRIPTION πŸ’–

So this function queries the VF's preemption timeout (PT) provisioning from all tiles/GTs β€” all of them, no cherry-picking. πŸ“

If the values across tiles/GTs are inconsistent, then -EUCLEAN error will be returned. 😭 That’s the vibe check, and it did not pass.

And the big important thing: this function can only be called on PF. PF only. Periodt. πŸ‘‘


πŸŽ€ RETURN πŸŽ€

0 on success or a negative error code on failure β€” that's the whole return situation, bestie. πŸ’«


πŸ”— SEE ALSO πŸ”—

Kernel file: ./drivers/gpu/drm/xe/xe_sriov_pf_provision.c πŸ“

okay bye bestie πŸ’– β€” source/version info: ./drivers/gpu/drm/xe; date: October 2026; and yes, this is the xe_sriov_pf..._query_vf_pt(9) page. Mwah 🫢✨

πŸ“¦ where this page comes from