Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: 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>
Subject: Re: [PATCH 00/11] Enable per exec queue MSI-X vector assignment
Date: Wed, 10 Jun 2026 16:51:04 -0700	[thread overview]
Message-ID: <ain4aHd9KLMh+2Fd@gsse-cloud1.jf.intel.com> (raw)
In-Reply-To: <20260610212833.153366-13-stuart.summers@intel.com>

On Wed, Jun 10, 2026 at 09:28:32PM +0000, Stuart Summers wrote:
> This series adds support for per exec queue MSI-X vector
> assignment as well as a per exec queue wait queue in the

There’s another improvement we should consider once we have MSIX per
queue: assigning a unique xe_hw_fence_irq to each queue with a valid
MSIX vector. In the MSIX IRQ handler, we could map from the vector to q
and only trigger that queue’s xe_hw_fence_irq.

This should reduce IRQ overhead, as we would walk the individual queue’s
list of pending jobs/fences rather than all pending jobs/fences within
an engine class. We could also introduce a variant of
hw_fence_irq_run_cb for MSIX that immediately bails when it encounters
an unsignaled fence, since the list in xe_hw_fence_irq would now signal
in order.

This can be done as a follow-up, but it should provide a significant win
in certain cases.

Matt

> 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.
> 
> v2: Drop the drm_dbg change patch
>     Directly call xe_hw_engine_handle_irq() from xe_memirq_hwe_handler()
>     Only add to ufence_list for user queues
> 
> Stuart Summers (11):
>   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: 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       | 51 ++++++++++++++++-
>  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              | 36 ++++++++++--
>  drivers/gpu/drm/xe/xe_irq.h              |  9 +++
>  drivers/gpu/drm/xe/xe_lrc.c              | 15 ++++-
>  drivers/gpu/drm/xe/xe_memirq.c           | 59 +++++++++-----------
>  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, 310 insertions(+), 51 deletions(-)
> 
> -- 
> 2.43.0
> 

  parent reply	other threads:[~2026-06-10 23:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 21:28 [PATCH 00/11] Enable per exec queue MSI-X vector assignment Stuart Summers
2026-06-10 21:28 ` [PATCH 01/11] drm/xe: Add kerneldoc to xe_wait_user_fence_ioctl() Stuart Summers
2026-06-10 21:28 ` [PATCH 02/11] drm/xe: Handle NULL in xe_exec_queue_get_unless_zero() Stuart Summers
2026-06-10 21:28 ` [PATCH 03/11] drm/xe: Cap MSI-X vector count to XE_MSIX_MAX_VECS Stuart Summers
2026-06-11 10:47   ` Maarten Lankhorst
2026-06-11 22:49     ` Summers, Stuart
2026-06-12  8:50       ` Maarten Lankhorst
2026-06-12 15:32         ` Summers, Stuart
2026-06-10 21:28 ` [PATCH 04/11] drm/xe: Assign dedicated MSI-X vectors to exec queues Stuart Summers
2026-06-10 21:28 ` [PATCH 05/11] drm/xe: Add configfs max_msix_vecs attribute Stuart Summers
2026-06-10 21:28 ` [PATCH 06/11] drm/xe: Remove memirq status and source checks for engine interrupts Stuart Summers
2026-06-10 21:28 ` [PATCH 07/11] drm/xe: Add per-exec-queue user fence wait queue Stuart Summers
2026-06-10 23:35   ` Matthew Brost
2026-06-11 22:50     ` Summers, Stuart
2026-06-10 21:28 ` [PATCH 08/11] drm/xe: Track all exec queues in a device-level ufence list Stuart Summers
2026-06-10 21:28 ` [PATCH 09/11] drm/xe: Hook up per queue thread wake to the unique MSI-X vector allocation Stuart Summers
2026-06-10 21:28 ` [PATCH 10/11] drm/xe: Enable per-queue ufence wake in ioctl and wake function Stuart Summers
2026-06-10 21:28 ` [PATCH 11/11] drm/xe/memirq: Enable compute walker post-sync interrupt Stuart Summers
2026-06-10 22:06 ` ✗ CI.checkpatch: warning for Enable per exec queue MSI-X vector assignment (rev2) Patchwork
2026-06-10 22:07 ` ✓ CI.KUnit: success " Patchwork
2026-06-10 22:59 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-10 23:51 ` Matthew Brost [this message]
2026-06-11 23:08   ` [PATCH 00/11] Enable per exec queue MSI-X vector assignment Summers, Stuart
2026-06-12  0:17     ` Matthew Brost
2026-06-11  6:58 ` ✓ Xe.CI.FULL: success for Enable per exec queue MSI-X vector assignment (rev2) 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=ain4aHd9KLMh+2Fd@gsse-cloud1.jf.intel.com \
    --to=matthew.brost@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=stuart.summers@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox