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 15/22] drm/xe: Add deadline Kconfig options
Date: Sun, 4 Jan 2026 20:02:30 -0800 [thread overview]
Message-ID: <20260105040237.1307873-16-matthew.brost@intel.com> (raw)
In-Reply-To: <20260105040237.1307873-1-matthew.brost@intel.com>
Add Kconfig options to tune the deadline manager behavior.
CONFIG_DRM_XE_DEADLINE_WINDOW_US configures the deadline window. If a
fence is not signaled within this window prior to the programmed
deadline, deadline boosting is activated. The default is 3000 us,
allowing OEMs to tune deadline sensitivity.
CONFIG_DRM_XE_DEADLINE_PRIO_BOOST_WINDOW_PERCENT configures the
percentage of the deadline window during which priority boosting is
applied in addition to frequency boosting.
CONFIG_DRM_XE_DEADLINE_EXIT_DELAY_MS configures the delay from the last
deadline signaling until the boost mode is exited.
v2:
- s/CONFIG_DRM_XE_DEADLINE_WINDOW/CONFIG_DRM_XE_DEADLINE_WINDOW_US
- Add priority boost percent Kconfig
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
---
drivers/gpu/drm/xe/Kconfig.profile | 22 ++++++++++++++++++++++
drivers/gpu/drm/xe/xe_deadline_mgr.c | 17 ++++++++++++++++-
2 files changed, 38 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/Kconfig.profile b/drivers/gpu/drm/xe/Kconfig.profile
index 594acedf7b56..e01e7cc11c53 100644
--- a/drivers/gpu/drm/xe/Kconfig.profile
+++ b/drivers/gpu/drm/xe/Kconfig.profile
@@ -60,3 +60,25 @@ config DRM_XE_ENABLE_SCHEDTIMEOUT_LIMIT
to apply to applicable user. For elevated user, all above MIN
and MAX values will apply when this configuration is enable to
apply limitation. By default limitation is applied.
+
+config DRM_XE_DEADLINE_WINDOW_US
+ int "Default deadline window (us)"
+ default 3000
+ help
+ Specifies the deadline window in microseconds. If a fence has not
+ been signaled when the current time is within this window of its
+ programmed deadline, deadline boosting is enabled.
+
+config DRM_XE_DEADLINE_PRIO_BOOST_WINDOW_PERCENT
+ int "Percent of deadline window with priority boost"
+ default 60
+ range 0 100
+ help
+ Specifies the percentage of the deadline window during which
+ priority boosting is applied in addition to frequency boosting.
+
+config DRM_XE_DEADLINE_EXIT_DELAY_MS
+ int "Default deadline exit delay (ms)"
+ default 100
+ help
+ Specifies the deadline exit delay in milliseconds.
diff --git a/drivers/gpu/drm/xe/xe_deadline_mgr.c b/drivers/gpu/drm/xe/xe_deadline_mgr.c
index 061664ed24e3..8ebecf92aa8c 100644
--- a/drivers/gpu/drm/xe/xe_deadline_mgr.c
+++ b/drivers/gpu/drm/xe/xe_deadline_mgr.c
@@ -11,9 +11,24 @@
#include "xe_gt.h"
#include "xe_hw_fence.h"
+#ifdef CONFIG_DRM_XE_DEADLINE_WINDOW_US
+#define XE_DEADLINE_WINDOW_US CONFIG_DRM_XE_DEADLINE_WINDOW_US
+#else
#define XE_DEADLINE_WINDOW_US 3000
-#define XE_DEADLINE_PRIO_BOOST_WINDOW_PERCENT 60
+#endif
+
+#ifdef CONFIG_DRM_XE_DEADLINE_PRIO_BOOST_WINDOW_PERCENT
+#define XE_DEADLINE_PRIO_BOOST_WINDOW_PERCENT \
+ CONFIG_DRM_XE_DEADLINE_PRIO_BOOST_WINDOW_PERCENT
+#else
+#define XE_DEADLINE_PRIO_BOOST_WINDOW_PERCENT 60
+#endif
+
+#ifdef CONFIG_DRM_XE_DEADLINE_EXIT_DELAY_MS
+#define XE_DEADLINE_EXIT_DELAY_MS CONFIG_DRM_XE_DEADLINE_EXIT_DELAY_MS
+#else
#define XE_DEADLINE_EXIT_DELAY_MS 100
+#endif
static ktime_t __xe_deadline_mgr_freq_boost_window(void)
{
--
2.34.1
next prev parent 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 [PATCH v2 00/22] Fence deadlines in Xe Matthew Brost
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 ` Matthew Brost [this message]
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-16-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