xe_gt_sriov_...meout_locked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_gt_sriov_pf_config_set_preempt_timeout_locked πŸ’…

okay so bestie, welcome to the Kernel API Manual</> (section 9, we're fancy here) β€” this is the page for xe_gt_sriov_pf_config_set_preempt_timeout_locked, and yes the page title really does get truncated like that in the header. iconic little ellipsis moment, no notes πŸ’€


✨ NAME ✨

xe_gt_sriov_pf_config_set_preempt_timeout_locked β€” literally just here to configure the PF/VF preemption timeout. that's it, that's the whole gig πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int xe_gt_sriov_pf_config_set_preempt_timeout_locked (struct xe_gt *gt ,
unsigned int vfid , u32 preempt_timeout );

🌸 ARGUMENTS 🌸

  • gt β€” the xe_gt 🫢 that's your graphics tile bestie, the whole reason we're here
  • vfid β€” the PF or VF identifier, like the little name tag telling us which function we're configuring
  • preempt_timeout β€” the preemption timeout you're requesting, measured in microseconds ⏱️ and heads up: 0 means infinity, which is a whole vibe ngl

πŸ”₯ DESCRIPTION πŸ”₯

okay so listen πŸ‘€ β€” this function can only be called on the PF, and only with the master mutex held. that's a hard requirement, not a suggestion, so don't come at it sideways.

the way it works is it'll log the provisioned value β€” or, if things go sideways, it logs the error instead. either way you get receipts πŸ“βœ¨

⚠️ lowkey important: PF only, and the master mutex must be held. this is not a "try it and see" situation bestie 😭

⭐ RETURN ⭐

0 on success β€” slay πŸ’– β€” or a negative error code on failure. that's the whole dealio.


πŸ‘‘ SEE ALSO πŸ‘‘

buckle up bestie, this list is long, and every single one of these deserves its moment in the spotlight 🌈

and the source file itself, bestie, right here in the kernel tree:

./drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c

πŸ’œ okay that's the whole page!! this lil number lives over in ./drivers/gpu/drm/xe, dated October 2026, and it's filed under xe_gt_sriov_...meout_locked(9) β€” go forth and configure those preemption timeouts responsibly, mutex in hand 🫢✨

πŸ“¦ where this page comes from