xe_sriov_pf_arm_guard(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_sriov_pf_arm_guard(9) β€” from the Kernel API Manual, bestie

okay so picture this: it's a Kernel API Manual page, the vibe is immaculate, and the main character is literally xe_sriov_pf_arm_guard. let's get into it πŸŽ€


✨ NAME ✨

xe_sriov_pf_arm_guard β€” arm the guard for exclusive/lockdown mode. that's it, that's the whole job. she locks things down, she arms the guard, she slays πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

int xe_sriov_pf_arm_guard (struct xe_device *xe , struct xe_guard *guard
, bool lockdown , void *who );

yes bestie, four arguments, one int back, no cap. copy it exactly like that, don't be cute with the spacing πŸ‘‘


🌸 ARGUMENTS 🌸

  • xe β€” the PF xe_device. like, the whole device. the main character energy of the parameter list.
  • guard β€” the xe_guard that's about to get armed. she's the one getting the glow-up ✨
  • lockdown β€” a bool that picks the mode: true means arm for lockdown mode, false means arm for exclusive mode. two modes, one flag, iconic honestly.
  • who β€” the address of the new owner 🫢 …or NULL if it's just the caller. your call, iykyk.

πŸ’œ DESCRIPTION πŸ’œ

first things first, the rule: this function can only be called on PF. not VF, not anybody else. PF only. periodt. πŸ™ˆ

other than that? she's a simple wrapper for xe_guard_arm, with some extra debug messages on top so you can actually see what's happening. lowkey the best kind of function β€” does the thing, then tells you about it πŸ”₯


⭐ RETURN ⭐

0 on success πŸŽ‰, or a negative error code on failure 😭. that's the whole story.


🌈 SEE ALSO 🌈

go read them all, they're all baddies, this is the group chat 🫢


ngl if you're arming a guard, you better be on PF. that's the whole vibe check. πŸ’€

and that's a wrap, babe 🧚 β€” this page lives in ./drivers/gpu/drm/xe, dated October 2026, and it's titled xe_sriov_pf_arm_guard(9). mwah πŸ’–

πŸ“¦ where this page comes from