From: Maarten Lankhorst <dev@lankhorst.se>
To: intel-xe@lists.freedesktop.org
Subject: [FOR CI 0/5] Testing PREEMPT_RT with disabling preemption in the most critical section.
Date: Wed, 29 Oct 2025 10:59:28 +0100 [thread overview]
Message-ID: <20251029095934.16813-1-dev@lankhorst.se> (raw)
Fix get_vblank_counter() and try to disable preemption in the most critical part of the code.
Maarten Lankhorst (3):
drm/i915/display: Make get_vblank_counter use intel_de_read_fw()
drm/xe/display: Disable preemption in the most critical section
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_vblank.c | 90 ++++++++++++++-------
drivers/gpu/drm/xe/Kconfig.debug | 5 ++
kernel/Kconfig.preempt | 4 +-
6 files changed, 111 insertions(+), 53 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-29 9:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 9:59 Maarten Lankhorst [this message]
2025-10-29 9:59 ` [FOR CI 1/5] drm/i915/display: Make get_vblank_counter use intel_de_read_fw() Maarten Lankhorst
2025-10-29 9:59 ` [FOR CI 2/5] drm/i915: Use preempt_disable/enable_rt() where recommended Maarten Lankhorst
2025-10-29 10:17 ` Jani Nikula
2025-10-29 9:59 ` [FOR CI 3/5] drm/i915: Don't disable interrupts on PREEMPT_RT during atomic updates Maarten Lankhorst
2025-10-29 9:59 ` [FOR CI 4/5] drm/xe/display: Disable preemption in the most critical section Maarten Lankhorst
2025-10-29 9:59 ` [FOR CI 5/5] PREEMPT_RT injection Maarten Lankhorst
2025-10-29 11:41 ` ✗ CI.checkpatch: warning for Testing PREEMPT_RT with disabling preemption in the most critical section Patchwork
2025-10-29 11:42 ` ✓ CI.KUnit: success " Patchwork
2025-10-29 12:05 ` ✗ CI.checksparse: warning " 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=20251029095934.16813-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