xe_exec_queu...operty_ioctl(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_exec_queue_set_property_ioctl ✨

okay so bestie, buckle up β€” this is a page from the Kernel API Manual and it's honestly serving very niche-core, but we're gonna get through it together 🫢 it's all about setting a property on an exec queue, and like… that's it, that's the vibe.


🌸 NAME 🌸

xe_exec_queue_set_property_ioctl β€” literally just set a property on an exec queue, no cap πŸ’…


✨ SYNOPSIS ✨

no thoughts, just the signature, copy-pasted exactly because we do not freestyle code around here:

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

πŸŽ€ ARGUMENTS πŸŽ€

three little guys walk into a function:

  • dev β€” the DRM device, aka the main character of this whole situation πŸ‘‘
  • data β€” the IOCTL data, the lil payload carrying the tea πŸ“
  • file β€” the DRM file, our backstage pass 🎟️

πŸ¦‹ DESCRIPTION πŸ¦‹

so what does it do? it lets you set properties on an existing exec queue β€” not creating one, not destroying one, just ✨adjusting✨ one that's already out here living its life.

and rn the only property it supports is setting multi-queue priority. that's the whole menu. one item. iconic minimalism honestly 🌈


πŸ’– RETURN πŸ’–

  • 0 on success β€” slay, we ate πŸŽ‰
  • a negative error code on failure β€” not slay, something went sideways 😭

🌟 SEE ALSO 🌟

the whole friend group, and yes we're tagging everyone because nobody gets left on read πŸ’œ

kernel file ./drivers/gpu/drm/xe/xe_exec_queue.c β€” the source of truth, the mothership:

like I said. the whole group chat. iykyk πŸ’€


and that's the page bestie!! this one lives under ./drivers/gpu/drm/xe, dated October 2026, in the Kernel API Manual, under the extremely truncated name xe_exec_queu...operty_ioctl(9) β€” go hydrate, drink some water, and go set some properties πŸ’œβœ¨πŸŽ€

πŸ“¦ where this page comes from