xe_guard_arm(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_guard_arm(9) β€” the guard-arming era

okay so bestie, welcome to xe_guard_arm(9), a page from the Kernel API Manual. no cap, this is the little function that decides who gets to hold the ✨guard✨ β€” keep reading, it's giving short-but-iconic.


🌸 NAME 🌸

xe_guard_arm β€” arm the guard for the exclusive/lockdown mode. literally that's the whole job. arm it. πŸ’ͺ

✨ SYNOPSIS ✨

int xe_guard_arm (struct xe_guard *guard , bool lockdown , void *who );

πŸŽ€ ARGUMENTS πŸŽ€

  • guard β€” the xe_guard to arm, bestie. this is the main character, the thing you're arming.
  • lockdown β€” arm for lockdown (true) or exclusive (false) mode. two moods, one bool. πŸ¦‹
  • who β€” optional owner info, and it's for debug only, so like… it's just there for the vibes and the forensics. πŸ™ˆ

πŸ’… DESCRIPTION πŸ’…

okay so here's the tea πŸ‘‘:

  • Multiple lockdown requests are allowed. like, the more the merrier, no gatekeeping.
  • Only a single exclusive access can be granted. one spot, one holder, periodt.
  • It will fail if the guard is already in exclusive mode. already taken? not your turn. πŸ’€
  • On success, you must call xe_guard_disarm to release. yes, MUST. don't just walk away holding it, that's not the vibe. 😭
no cap on this one: if xe_guard_arm succeeds, xe_guard_disarm is not optional β€” it's how you give the guard back. 🫢

πŸ”₯ RETURN πŸ”₯

0 on success or a negative error code on failure. slay when it's 0, check the negative when it's not. ⭐

🌈 SEE ALSO 🌈

go read those next, iykyk 🧚


πŸ’– that's the whole page, bestie β€” from ./drivers/gpu/drm/xe, dated October 2026, and yes the footer says xe_guard_arm(9) too, we love a consistent queen. mwah, drink water, and remember to disarm πŸ’œ

πŸ“¦ where this page comes from