Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <dev@lankhorst.se>
To: intel-xe@lists.freedesktop.org
Subject: [FOR CI 0/5] Testing PREEMPT_RT with disabling interrupts in the most critical section.
Date: Thu, 23 Oct 2025 10:55:56 +0200	[thread overview]
Message-ID: <20251023085601.90831-1-dev@lankhorst.se> (raw)

Only disable preemption in this series.

Maarten Lankhorst (3):
  drm/xe: Bump xe_device_l2_flush even higher
  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 | 81 ++++++++++++++-------
 drivers/gpu/drm/xe/Kconfig.debug            |  5 ++
 drivers/gpu/drm/xe/xe_device.c              |  4 +-
 kernel/Kconfig.preempt                      |  4 +-
 7 files changed, 108 insertions(+), 51 deletions(-)

-- 
2.51.0


             reply	other threads:[~2025-10-23  8:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-23  8:55 Maarten Lankhorst [this message]
2025-10-23  8:55 ` [FOR CI 1/5] drm/xe: Bump xe_device_l2_flush even higher Maarten Lankhorst
2025-10-23  8:55 ` [FOR CI 2/5] drm/i915: Use preempt_disable/enable_rt() where recommended Maarten Lankhorst
2025-10-23  8:55 ` [FOR CI 3/5] drm/i915: Don't disable interrupts on PREEMPT_RT during atomic updates Maarten Lankhorst
2025-10-23  8:56 ` [FOR CI 4/5] drm/xe/display: Disable preemption in the most critical section Maarten Lankhorst
2025-10-23  8:56 ` [FOR CI 5/5] PREEMPT_RT injection Maarten Lankhorst
2025-10-23 13:38 ` ✗ CI.checkpatch: warning for Testing PREEMPT_RT with disabling interrupts in the most critical section. (rev2) Patchwork
2025-10-23 13:39 ` ✓ CI.KUnit: success " Patchwork
2025-10-23 14:00 ` ✗ CI.checksparse: warning " Patchwork
2025-10-23 22:15 ` ✗ Xe.CI.Full: failure " Patchwork
2025-10-27 10:03 ` ✗ CI.checkpatch: warning for Testing PREEMPT_RT with disabling interrupts in the most critical section. (rev3) Patchwork
2025-10-27 10:04 ` ✓ CI.KUnit: success " Patchwork
2025-10-27 10:18 ` ✗ CI.checksparse: warning " Patchwork
2025-10-27 10:47 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-10-27 12:52 ` ✗ Xe.CI.Full: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2025-10-17 15:37 [FOR CI 0/5] Testing PREEMPT_RT with disabling interrupts in the most critical section Maarten Lankhorst

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=20251023085601.90831-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