From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: daniele.ceraolospurio@intel.com, carlos.santa@intel.com
Subject: [PATCH v2 00/22] Fence deadlines in Xe
Date: Sun, 4 Jan 2026 20:02:15 -0800 [thread overview]
Message-ID: <20260105040237.1307873-1-matthew.brost@intel.com> (raw)
This series introduces deadline support for exported scheduler fences.
When a deadline is set on a fence, the driver attempts to complete the
work within a configurable window (default 3 ms, via Kconfig) ahead of
the deadline.
As the deadline approaches, the exec queue first receives a frequency
boost. If the queue has CAP_SYS_ADMIN privileges, a later stage also
applies a priority boost. This tiered approach allows work to run at the
same baseline priority as the application, only increasing priority when
a deadline is at risk of being missed.
The primary use case is compositors that target a stable frame cadence
while avoiding a permanently elevated scheduling priority.
Lightly tested with an IGT and running display; behavior appears
correct.
VLK-82801
IGT: https://patchwork.freedesktop.org/series/159616/
v2:
- Fully implemented deadline manager
- Separate frequency and priority boost windows
- Enable deadlines in Intel display
Matt
Matthew Brost (22):
drm/xe: Add dedicated message lock
drm/xe: Add EXEC_QUEUE_FLAG_CAP_SYS_NICE
drm/xe: Store exec queue in hardware fence
drm/xe: Add deadline exec queue vfuncs
drm/xe: Export to_xe_hw_fence
drm/xe: Export xe_hw_fence_signaled
drm/xe: Implement deadline manager
drm/xe: Initialize deadline manager on exec queues
drm/xe: Stub out execlists deadline vfuncs as NOPs
drm/xe: Make scheduler message lock IRQ-safe
drm/xe: Support unstable opcodes for static scheduler messages
drm/xe: Implement GuC submission backend ops for deadlines
drm/xe: Enable deadlines on hardware fences
drm/xe: Fix Kconfig.profile newlines
drm/xe: Add deadline Kconfig options
drm/xe: Add exec queue deadline trace points
drm/xe: Add hw fence deadline trace points
drm/xe: Add timestamp_ms to LRC snapshot
drm/xe: Enforce GuC static message defines
drm/xe: Document the deadline manager
drm/atomic: Export fence deadline helper for atomic commits
drm/i915/display: Use atomic helper to set plane fence deadlines
drivers/gpu/drm/drm_atomic_helper.c | 11 +-
drivers/gpu/drm/i915/display/intel_display.c | 2 +
drivers/gpu/drm/xe/Kconfig.profile | 29 ++
drivers/gpu/drm/xe/Makefile | 1 +
drivers/gpu/drm/xe/xe_deadline_mgr.c | 463 +++++++++++++++++++
drivers/gpu/drm/xe/xe_deadline_mgr.h | 26 ++
drivers/gpu/drm/xe/xe_deadline_mgr_types.h | 52 +++
drivers/gpu/drm/xe/xe_exec_queue.c | 11 +
drivers/gpu/drm/xe/xe_exec_queue_types.h | 15 +
drivers/gpu/drm/xe/xe_execlist.c | 15 +
drivers/gpu/drm/xe/xe_gpu_scheduler.c | 43 +-
drivers/gpu/drm/xe/xe_gpu_scheduler.h | 17 +-
drivers/gpu/drm/xe/xe_gpu_scheduler_types.h | 4 +-
drivers/gpu/drm/xe/xe_guc_exec_queue_types.h | 2 +-
drivers/gpu/drm/xe/xe_guc_submit.c | 170 +++++--
drivers/gpu/drm/xe/xe_hw_fence.c | 38 +-
drivers/gpu/drm/xe/xe_hw_fence.h | 7 +-
drivers/gpu/drm/xe/xe_hw_fence_types.h | 19 +
drivers/gpu/drm/xe/xe_lrc.c | 10 +-
drivers/gpu/drm/xe/xe_lrc.h | 4 +-
drivers/gpu/drm/xe/xe_sched_job.c | 5 +-
drivers/gpu/drm/xe/xe_trace.h | 42 +-
include/drm/drm_atomic_helper.h | 3 +
23 files changed, 918 insertions(+), 71 deletions(-)
create mode 100644 drivers/gpu/drm/xe/xe_deadline_mgr.c
create mode 100644 drivers/gpu/drm/xe/xe_deadline_mgr.h
create mode 100644 drivers/gpu/drm/xe/xe_deadline_mgr_types.h
--
2.34.1
next reply other threads:[~2026-01-05 4:02 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 4:02 Matthew Brost [this message]
2026-01-05 4:02 ` [PATCH v2 01/22] drm/xe: Add dedicated message lock Matthew Brost
2026-01-05 4:02 ` [PATCH v2 02/22] drm/xe: Add EXEC_QUEUE_FLAG_CAP_SYS_NICE Matthew Brost
2026-02-05 16:00 ` Rodrigo Vivi
2026-01-05 4:02 ` [PATCH v2 03/22] drm/xe: Store exec queue in hardware fence Matthew Brost
2026-02-05 16:02 ` Rodrigo Vivi
2026-01-05 4:02 ` [PATCH v2 04/22] drm/xe: Add deadline exec queue vfuncs Matthew Brost
2026-02-05 16:03 ` Rodrigo Vivi
2026-01-05 4:02 ` [PATCH v2 05/22] drm/xe: Export to_xe_hw_fence Matthew Brost
2026-01-05 4:02 ` [PATCH v2 06/22] drm/xe: Export xe_hw_fence_signaled Matthew Brost
2026-01-05 4:02 ` [PATCH v2 07/22] drm/xe: Implement deadline manager Matthew Brost
2026-01-05 4:02 ` [PATCH v2 08/22] drm/xe: Initialize deadline manager on exec queues Matthew Brost
2026-01-05 4:02 ` [PATCH v2 09/22] drm/xe: Stub out execlists deadline vfuncs as NOPs Matthew Brost
2026-01-05 4:02 ` [PATCH v2 10/22] drm/xe: Make scheduler message lock IRQ-safe Matthew Brost
2026-01-05 4:02 ` [PATCH v2 11/22] drm/xe: Support unstable opcodes for static scheduler messages Matthew Brost
2026-01-05 4:02 ` [PATCH v2 12/22] drm/xe: Implement GuC submission backend ops for deadlines Matthew Brost
2026-01-10 10:48 ` kernel test robot
2026-01-05 4:02 ` [PATCH v2 13/22] drm/xe: Enable deadlines on hardware fences Matthew Brost
2026-01-05 4:02 ` [PATCH v2 14/22] drm/xe: Fix Kconfig.profile newlines Matthew Brost
2026-02-05 16:06 ` Rodrigo Vivi
2026-01-05 4:02 ` [PATCH v2 15/22] drm/xe: Add deadline Kconfig options Matthew Brost
2026-01-05 4:02 ` [PATCH v2 16/22] drm/xe: Add exec queue deadline trace points Matthew Brost
2026-01-05 4:02 ` [PATCH v2 17/22] drm/xe: Add hw fence " Matthew Brost
2026-01-05 4:02 ` [PATCH v2 18/22] drm/xe: Add timestamp_ms to LRC snapshot Matthew Brost
2026-01-05 4:02 ` [PATCH v2 19/22] drm/xe: Enforce GuC static message defines Matthew Brost
2026-01-05 4:02 ` [PATCH v2 20/22] drm/xe: Document the deadline manager Matthew Brost
2026-01-05 4:02 ` [PATCH v2 21/22] drm/atomic: Export fence deadline helper for atomic commits Matthew Brost
2026-01-05 4:02 ` [PATCH v2 22/22] drm/i915/display: Use atomic helper to set plane fence deadlines Matthew Brost
2026-01-05 4:09 ` ✗ CI.checkpatch: warning for Fence deadlines in Xe (rev2) Patchwork
2026-01-05 4:10 ` ✓ CI.KUnit: success " Patchwork
2026-01-05 4:26 ` ✗ CI.checksparse: warning " Patchwork
2026-01-05 5:07 ` ✓ Xe.CI.BAT: success " Patchwork
2026-01-05 6:51 ` ✗ Xe.CI.Full: failure " 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=20260105040237.1307873-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=carlos.santa@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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