From: Stuart Summers <stuart.summers@intel.com>
Cc: michal.wajdeczko@intel.com, ilia.levi@intel.com,
x.wang@intel.com, rodrigo.vivi@intel.com,
intel-xe@lists.freedesktop.org,
alan.previn.teres.alexis@intel.com,
Stuart Summers <stuart.summers@intel.com>
Subject: [PATCH 00/12] Enable per exec queue MSI-X vector assignment
Date: Fri, 5 Jun 2026 23:21:07 +0000 [thread overview]
Message-ID: <20260605232108.674580-14-stuart.summers@intel.com> (raw)
This series adds support for per exec queue MSI-X vector
assignment as well as a per exec queue wait queue in the
wait user fence ioctl. MSI-X vectors are dynamically assigned
during exec queue creation up to a set maximum. Once the max
is reached, everything else falls back to the default vector.
These dynamic vectors allow us to wake up a targeted wait
queue and user thread instead of broadcasting out to all
potential user threads like we're doing today. This is interesting
when we have many user threads outstanding as we don't want
to wake them up in a storm for each interrupt coming in.
Additionally, there have been changes in the memirq code lately
to isolate some of the interrupts handled here. Starting with
xe3p, however, we have new interrupts available for compute walker
post sync interrupts. Currently these are enabled for legacy MSI
use cases, but the bits are also available for MSI-X. Enable
those bits here.
Stuart Summers (12):
drm/xe: Add kerneldoc to xe_wait_user_fence_ioctl()
drm/xe: Handle NULL in xe_exec_queue_get_unless_zero()
drm/xe: Cap MSI-X vector count to XE_MSIX_MAX_VECS
drm/xe: Assign dedicated MSI-X vectors to exec queues
drm/xe: Add configfs max_msix_vecs attribute
drm/xe: Change MSI-X assignment failure to drm_dbg
drm/xe: Remove memirq status and source checks for engine interrupts
drm/xe: Add per-exec-queue user fence wait queue
drm/xe: Track all exec queues in a device-level ufence list
drm/xe: Hook up per queue thread wake to the unique MSI-X vector
allocation
drm/xe: Enable per-queue ufence wake in ioctl and wake function
drm/xe/memirq: Enable compute walker post-sync interrupt
drivers/gpu/drm/xe/regs/xe_lrc_layout.h | 3 +
drivers/gpu/drm/xe/xe_configfs.c | 71 ++++++++++++++++++++++++
drivers/gpu/drm/xe/xe_configfs.h | 6 ++
drivers/gpu/drm/xe/xe_device.c | 2 +
drivers/gpu/drm/xe/xe_device_types.h | 11 ++++
drivers/gpu/drm/xe/xe_exec_queue.c | 47 +++++++++++++++-
drivers/gpu/drm/xe/xe_exec_queue.h | 2 +-
drivers/gpu/drm/xe/xe_exec_queue_types.h | 6 ++
drivers/gpu/drm/xe/xe_guc_submit.c | 6 +-
drivers/gpu/drm/xe/xe_hw_engine.c | 6 +-
drivers/gpu/drm/xe/xe_hw_engine.h | 3 +-
drivers/gpu/drm/xe/xe_irq.c | 38 +++++++++++--
drivers/gpu/drm/xe/xe_irq.h | 9 +++
drivers/gpu/drm/xe/xe_lrc.c | 15 ++++-
drivers/gpu/drm/xe/xe_memirq.c | 54 +++++++++---------
drivers/gpu/drm/xe/xe_memirq.h | 4 +-
drivers/gpu/drm/xe/xe_sync.c | 3 +-
drivers/gpu/drm/xe/xe_wait_user_fence.c | 64 ++++++++++++++++++++-
drivers/gpu/drm/xe/xe_wait_user_fence.h | 4 ++
19 files changed, 308 insertions(+), 46 deletions(-)
--
2.43.0
next reply other threads:[~2026-06-05 23:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 23:21 Stuart Summers [this message]
2026-06-05 23:21 ` [PATCH 01/12] drm/xe: Add kerneldoc to xe_wait_user_fence_ioctl() Stuart Summers
2026-06-05 23:21 ` [PATCH 02/12] drm/xe: Handle NULL in xe_exec_queue_get_unless_zero() Stuart Summers
2026-06-05 23:21 ` [PATCH 03/12] drm/xe: Cap MSI-X vector count to XE_MSIX_MAX_VECS Stuart Summers
2026-06-05 23:21 ` [PATCH 04/12] drm/xe: Assign dedicated MSI-X vectors to exec queues Stuart Summers
2026-06-05 23:21 ` [PATCH 05/12] drm/xe: Add configfs max_msix_vecs attribute Stuart Summers
2026-06-05 23:21 ` [PATCH 06/12] drm/xe: Change MSI-X assignment failure to drm_dbg Stuart Summers
2026-06-06 10:57 ` Michal Wajdeczko
2026-06-08 20:30 ` Summers, Stuart
2026-06-05 23:21 ` [PATCH 07/12] drm/xe: Remove memirq status and source checks for engine interrupts Stuart Summers
2026-06-06 11:18 ` Michal Wajdeczko
2026-06-05 23:21 ` [PATCH 08/12] drm/xe: Add per-exec-queue user fence wait queue Stuart Summers
2026-06-05 23:21 ` [PATCH 09/12] drm/xe: Track all exec queues in a device-level ufence list Stuart Summers
2026-06-05 23:21 ` [PATCH 10/12] drm/xe: Hook up per queue thread wake to the unique MSI-X vector allocation Stuart Summers
2026-06-05 23:21 ` [PATCH 11/12] drm/xe: Enable per-queue ufence wake in ioctl and wake function Stuart Summers
2026-06-05 23:21 ` [PATCH 12/12] drm/xe/memirq: Enable compute walker post-sync interrupt Stuart Summers
2026-06-05 23:47 ` ✗ CI.checkpatch: warning for Enable per exec queue MSI-X vector assignment Patchwork
2026-06-05 23:49 ` ✓ CI.KUnit: success " Patchwork
2026-06-06 0:43 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-06 13:27 ` ✓ Xe.CI.FULL: " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260605232108.674580-14-stuart.summers@intel.com \
--to=stuart.summers@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=ilia.levi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.wajdeczko@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=x.wang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.