From: Maarten Lankhorst <dev@lankhorst.se>
To: intel-xe@lists.freedesktop.org
Subject: [FOR CI 0/5] drm/xe/display: Disable migration for the critical
Date: Tue, 21 Oct 2025 14:43:04 +0200 [thread overview]
Message-ID: <20251021124309.130121-1-dev@lankhorst.se> (raw)
Using the principle of minimal impact to latency possible, only prevent migration
from occurring first.
Maarten Lankhorst (3):
drm/xe: Bump xe_device_l2_flush even higher
drm/xe/display: Disable migration in the most critical section
[FOR-CI] PREEMPT_RT injection
Mike Galbraith (2):
drm/i915: Use preempt_disable/enable_rt() where recommended
drm/i915: Don't disable interrupts on PREEMPT_RT during atomic updates
drivers/gpu/drm/i915/Kconfig.debug | 15 ------
drivers/gpu/drm/i915/display/intel_crtc.c | 23 ++++++--
drivers/gpu/drm/i915/display/intel_cursor.c | 27 ++++++++--
drivers/gpu/drm/i915/display/intel_dmc.c | 4 +-
drivers/gpu/drm/i915/display/intel_vblank.c | 58 ++++++++++++++++-----
drivers/gpu/drm/xe/Kconfig.debug | 5 ++
drivers/gpu/drm/xe/xe_device.c | 4 +-
kernel/Kconfig.preempt | 3 +-
8 files changed, 98 insertions(+), 41 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-21 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 12:43 Maarten Lankhorst [this message]
2025-10-21 12:43 ` [FOR CI 1/5] drm/xe: Bump xe_device_l2_flush even higher Maarten Lankhorst
2025-10-21 12:43 ` [FOR CI 2/5] drm/i915: Use preempt_disable/enable_rt() where recommended Maarten Lankhorst
2025-10-21 12:43 ` [FOR CI 3/5] drm/i915: Don't disable interrupts on PREEMPT_RT during atomic updates Maarten Lankhorst
2025-10-21 12:43 ` [FOR CI 4/5] drm/xe/display: Disable migration in the most critical section Maarten Lankhorst
2025-10-21 12:43 ` [FOR CI 5/5] [FOR-CI] PREEMPT_RT injection Maarten Lankhorst
2025-10-21 15:08 ` ✗ CI.checkpatch: warning for drm/xe/display: Disable migration for the critical Patchwork
2025-10-21 15:08 ` ✗ CI.KUnit: 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=20251021124309.130121-1-dev@lankhorst.se \
--to=dev@lankhorst.se \
--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