DRM_IVPU_CAP_MANAGE_CMDQ(9)

✨ DRM_IVPU_CAP_MANAGE_CMDQ ✨

okay so bestie, welcome to the Kernel API Manual — this one's a capability flag, DRM_IVPU_CAP_MANAGE_CMDQ, and it's giving very "let me handle my own queue" energy 💅

---

🌸 NAME 🌸

DRM_IVPU_CAP_MANAGE_CMDQ — and that's literally it, that's the whole name, no description attached, iconic minimalism 🎀

---

🦋 SYNOPSIS 🦋

DRM_IVPU_CAP_MANAGE_CMDQ

---

💖 DESCRIPTION 💖

so what does it actually do? the driver supports explicit command queue operations, bestie ✨ and those operations are:

• command queue create 🫶
• command queue destroy 💀
• submit job on a specific command queue 🔥

that's the vibe check — you get to be main character of your own command queue, no cap 👑

---

⭐ SEE ALSO ⭐

like, go read these too, they're all connected, iykyk 🌈

• Kernel file ./include/uapi/drm/ivpu_accel.h contexts(9)
• DRM_IVPU_CAP_METRIC_STREAMER(9)
• DRM_IVPU_CAP_DMA_MEMORY_RANGE(9)
• DRM_IVPU_CAP_BO_CREATE_FROM_USERPTR(9)
• struct drm_ivpu_param(9)
• struct drm_ivpu_bo_create(9)
• struct drm_ivpu_bo_create_from_userptr(9)
• struct drm_ivpu_bo_info(9)
• struct drm_ivpu_submit(9)
• struct drm_ivpu_cmdq_submit(9)
• struct drm_ivpu_bo_wait(9)
• struct drm_ivpu_metric_streamer_start(9)
• struct drm_ivpu_metric_streamer_get_data(9)
• struct drm_ivpu_cmdq_create(9)
• struct drm_ivpu_cmdq_destroy(9)
• struct drm_ivpu_metric_streamer_stop(9)

---

💌 ok that's the whole page, bestie — no bugs, no warnings, no env vars, just pure capability-flag goodness. slay 🧚

signed off with love from ./include/uapi/drm — drop date: October 2026 💖 (yes the manpage itself is a libra, we don't know, just roll with it) 🍓