xe_exec_queu...operty_ioctl(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME

ok so bestie, this page is literally about xe_exec_queue_get_property_ioctl β€” the kernel API manual one, section 9 β€” and its whole personality is: get a property from an exec queue. that's it, that's the vibe ✨ (the full title gets squished in the header as xe_exec_queu...operty_ioctl(9) because terminal headers are dramatic and cut you off mid-sentence, iykyk 🫢)


🌸 SYNOPSIS

int xe_exec_queue_get_property_ioctl (struct drm_device *dev , void
*data , struct drm_file *file );

no cap, that's the whole signature πŸŽ€


🎯 ARGUMENTS

  • dev β€” the DRM device, AKA the main character πŸ‘‘
  • data β€” the IOCTL data, the lil payload carrier 🎁
  • file β€” the DRM file, doing its supporting-role thing 🌈

πŸ’– DESCRIPTION

okay so, lowkey what this does: it retrieves property values from an existing exec queue. very "grabbing the receipts" energy fr fr 🧚

right now it currently supports getting the ban/reset status β€” like, is this queue slaying or has it been quietly sent to the shadow realm πŸ’€ that's the only property on the menu so far.


⭐ RETURN

  • 0 on success, with the value filled in β€” ate and left no crumbs πŸ’…
  • a negative error code on failure β€” not slay, but at least it tells you πŸ™ˆ

πŸ”₯ SEE ALSO

bestie that list is long enough to be its own group chat 😭 but every single one is a real one, go read them 🫢

πŸ¦‹ SIGN-OFF

and that's the page!! it lives in ./drivers/gpu/drm/xe, stamped October 2026, and drops the header xe_exec_queu...operty_ioctl(9) one more time on the way out because tradition πŸ’œβœ¨ go get those exec queue properties, queen πŸ‘‘

πŸ“¦ where this page comes from