From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: francois.dugast@intel.com, thomas.hellstrom@linux.intel.com,
michal.mrozek@intel.com
Subject: [PATCH 0/6] Fix performance when pagefaults and 3d/display share resources
Date: Thu, 11 Dec 2025 13:00:26 -0800 [thread overview]
Message-ID: <20251211210032.1520113-1-matthew.brost@intel.com> (raw)
xello_raytracer [1] showed a significant performance regression (~40×
slowdown) when the compute UMD enabled page faults. The issue was traced
to the implementation that allows page-fault workloads and dma-fence
workloads (3D/display) to coexist.
This series fixes several issues, bringing page-fault performance in
this benchmark to within 6% of preempt-fence mode (no page faults).
Matt
[1] https://github.com/intel-sandbox/xello_raytracer
Matthew Brost (6):
drm/xe: Adjust long-running workload timeslices to reasonable values
drm/xe: Use usleep_range for accurate long-running workload
timeslicing
drm/xe: Add debugfs knobs to control long running workload timeslicing
drm/xe: Skip exec queue schedule toggle if queue is idle during
suspend
drm/xe: Wait on in-syncs when swicthing to dma-fence mode
drm/xe: Add more GT stats around pagefault mode switch flows
drivers/gpu/drm/xe/xe_debugfs.c | 74 +++++++++++++++++++++++++
drivers/gpu/drm/xe/xe_device.c | 1 +
drivers/gpu/drm/xe/xe_device_types.h | 6 ++
drivers/gpu/drm/xe/xe_exec.c | 3 +-
drivers/gpu/drm/xe/xe_exec_queue.h | 17 ++++++
drivers/gpu/drm/xe/xe_gt_stats.c | 6 ++
drivers/gpu/drm/xe/xe_gt_stats_types.h | 3 +
drivers/gpu/drm/xe/xe_guc_submit.c | 46 +++++++++++++--
drivers/gpu/drm/xe/xe_hw_engine_group.c | 66 +++++++++++++++++++---
drivers/gpu/drm/xe/xe_hw_engine_group.h | 4 +-
drivers/gpu/drm/xe/xe_sync.c | 14 +++++
drivers/gpu/drm/xe/xe_sync.h | 1 +
drivers/gpu/drm/xe/xe_vm.c | 5 +-
drivers/gpu/drm/xe/xe_vm_types.h | 2 +-
14 files changed, 232 insertions(+), 16 deletions(-)
--
2.34.1
next reply other threads:[~2025-12-11 21:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 21:00 Matthew Brost [this message]
2025-12-11 21:00 ` [PATCH 1/6] drm/xe: Adjust long-running workload timeslices to reasonable values Matthew Brost
2025-12-11 21:00 ` [PATCH 2/6] drm/xe: Use usleep_range for accurate long-running workload timeslicing Matthew Brost
2025-12-11 21:00 ` [PATCH 3/6] drm/xe: Add debugfs knobs to control long running " Matthew Brost
2025-12-11 21:00 ` [PATCH 4/6] drm/xe: Skip exec queue schedule toggle if queue is idle during suspend Matthew Brost
2025-12-11 21:00 ` [PATCH 5/6] drm/xe: Wait on in-syncs when swicthing to dma-fence mode Matthew Brost
2025-12-12 9:22 ` Thomas Hellström
2025-12-12 16:33 ` Matthew Brost
2025-12-12 16:38 ` Matthew Brost
2025-12-12 18:41 ` Thomas Hellström
2025-12-12 20:20 ` Matthew Brost
2025-12-11 21:00 ` [PATCH 6/6] drm/xe: Add more GT stats around pagefault mode switch flows Matthew Brost
2025-12-12 16:07 ` Francois Dugast
2025-12-12 16:18 ` Matthew Brost
2025-12-11 21:29 ` ✓ CI.KUnit: success for Fix performance when pagefaults and 3d/display share resources Patchwork
2025-12-11 22:34 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-12-12 13:46 ` ✗ 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=20251211210032.1520113-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=francois.dugast@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.mrozek@intel.com \
--cc=thomas.hellstrom@linux.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