From: sashiko-bot@kernel.org
To: "Maarten Lankhorst" <dev@lankhorst.se>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v8 08/27] drm/i915: Use preempt_disable/enable_rt() where recommended
Date: Mon, 15 Jun 2026 20:32:39 +0000 [thread overview]
Message-ID: <20260615203240.0BEF61F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260615201846.307297-9-dev@lankhorst.se>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Removal of atomic context protection (interrupt and preemption disabling) during time-critical vblank register reads for the Xe driver on non-RT kernels.
--
commit 4b863f1335422d07b094a5072752ea5c148f7cbc
Author: Mike Galbraith <umgwanakikbuti@gmail.com>
drm/i915: Use preempt_disable/enable_rt() where recommended
This commit replaces unconditional local_irq_save() calls with a new
intel_vblank_section_enter_irqf() helper and adds conditional
preempt_disable() for PREEMPT_RT during vblank timestamping.
> diff --git a/drivers/gpu/drm/i915/display/intel_vblank.c b/drivers/gpu/drm/i915/display/intel_vblank.c
> index 6f1fa952b5391..07dca05332e5b 100644
> --- a/drivers/gpu/drm/i915/display/intel_vblank.c
> +++ b/drivers/gpu/drm/i915/display/intel_vblank.c
[ ... ]
> @@ -324,6 +338,17 @@ static void intel_vblank_section_enter(struct intel_display *display)
> static void intel_vblank_section_exit(struct intel_display *display)
> {
> }
> +
> +static void intel_vblank_section_enter_irqf(struct intel_display *display, unsigned long *flags)
> +{
> + *flags = 0;
> +}
> +
> +static void intel_vblank_section_exit_irqf(struct intel_display *display, unsigned long flags)
> +{
> + if (flags)
> + return;
> +}
> #endif
>
> static bool i915_get_crtc_scanoutpos(struct drm_crtc *_crtc,
> @@ -360,10 +385,10 @@ static bool i915_get_crtc_scanoutpos(struct drm_crtc *_crtc,
> * timing critical raw register reads, potentially with
> * preemption disabled, so the following code must not block.
> */
> - local_irq_save(irqflags);
> - intel_vblank_section_enter(display);
> + intel_vblank_section_enter_irqf(display, &irqflags);
>
> - /* preempt_disable_rt() should go right here in PREEMPT_RT patchset. */
> + if (IS_ENABLED(CONFIG_PREEMPT_RT))
> + preempt_disable();
[Severity: High]
Does this leave the timing-critical vblank register reads completely
unprotected on non-RT kernels when the #else path is taken?
Previously, local_irq_save() was unconditionally called to protect the
timestamping delta. With this change, the #else implementation of
intel_vblank_section_enter_irqf() is a no-op. Because preempt_disable()
is now strictly guarded by CONFIG_PREEMPT_RT, a standard non-RT kernel
taking this path executes with both interrupts and preemption enabled.
Could this allow random latency spikes during context switches or
interrupts, artificially inflating the delta between stime and etime
and resulting in timestamping failures?
>
> /* Get optional system timestamp before query. */
> if (stime)
[ ... ]
> @@ -468,13 +493,11 @@ int intel_get_crtc_scanline(struct intel_crtc *crtc)
> unsigned long irqflags;
> int position;
>
> - local_irq_save(irqflags);
> - intel_vblank_section_enter(display);
> + intel_vblank_section_enter_irqf(display, &irqflags);
>
> position = __intel_get_crtc_scanline(crtc);
>
> - intel_vblank_section_exit(display);
> - local_irq_restore(irqflags);
> + intel_vblank_section_exit_irqf(display, irqflags);
[Severity: High]
Similarly, does this leave __intel_get_crtc_scanline() entirely unprotected
from interrupts and preemption when the #else path is used on non-RT kernels?
>
> return position;
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260615201846.307297-1-dev@lankhorst.se?part=8
next prev parent reply other threads:[~2026-06-15 20:32 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 20:18 [PATCH v8 00/27] drm/i915/display: All patches to make PREEMPT_RT work on i915 + xe Maarten Lankhorst
2026-06-15 20:18 ` [PATCH v8 01/27] drm/vblank_work: Add methods to schedule vblank_work in 2 stages Maarten Lankhorst
2026-06-15 20:30 ` sashiko-bot
2026-06-15 20:18 ` [PATCH v8 02/27] drm/vblank: Add a 2-stage version of drm_crtc_arm_vblank_event Maarten Lankhorst
2026-06-15 20:31 ` sashiko-bot
2026-06-15 20:18 ` [PATCH v8 03/27] drm/intel/display: Make intel_crtc_arm_vblank_event static Maarten Lankhorst
2026-06-15 20:18 ` [PATCH v8 04/27] drm/intel/display: Convert vblank event handling to 2-stage arming Maarten Lankhorst
2026-06-15 20:35 ` sashiko-bot
2026-06-15 20:18 ` [PATCH v8 05/27] drm/i915/display: Move vblank put until after critical section Maarten Lankhorst
2026-06-15 20:25 ` sashiko-bot
2026-06-15 20:18 ` [PATCH v8 06/27] drm/i915/display: Remove locking from intel_vblank_evade " Maarten Lankhorst
2026-06-15 20:39 ` sashiko-bot
2026-06-15 20:18 ` [PATCH v8 07/27] drm/i915/display: Handle vlv dsi workaround in scanline_in_safe_range too Maarten Lankhorst
2026-06-15 20:29 ` sashiko-bot
2026-06-15 20:18 ` [PATCH v8 08/27] drm/i915: Use preempt_disable/enable_rt() where recommended Maarten Lankhorst
2026-06-15 20:32 ` sashiko-bot [this message]
2026-06-15 20:18 ` [PATCH v8 09/27] drm/i915/display: Make get_vblank_counter use intel_de_read_fw() Maarten Lankhorst
2026-06-15 20:39 ` sashiko-bot
2026-06-15 20:18 ` [PATCH v8 10/27] drm/i915/display: Do not take uncore lock in i915_get_vblank_counter Maarten Lankhorst
2026-06-15 20:35 ` sashiko-bot
2026-06-15 20:18 ` [PATCH v8 11/27] drm/i915/display: Make icl_dsi_frame_update use _fw too Maarten Lankhorst
2026-06-15 20:18 ` [PATCH v8 12/27] drm/i915/display: Use intel_de_read/write_fw in colorops Maarten Lankhorst
2026-06-15 20:18 ` [PATCH v8 13/27] drm/i915/display: Use intel_de_write_fw in intel_pipe_fastset Maarten Lankhorst
2026-06-15 20:46 ` sashiko-bot
2026-06-15 20:18 ` [PATCH v8 14/27] drm/i915/display: Make set_pipeconf use the fw variants Maarten Lankhorst
2026-06-15 20:44 ` sashiko-bot
2026-06-15 20:18 ` [PATCH v8 15/27] drm/i915/gt: Use spin_lock_irq() instead of local_irq_disable() + spin_lock() Maarten Lankhorst
2026-06-15 20:39 ` sashiko-bot
2026-06-15 20:18 ` [PATCH v8 16/27] drm/i915: Drop the irqs_disabled() check Maarten Lankhorst
2026-06-15 20:18 ` [PATCH v8 17/27] drm/i915/guc: Consider also RCU depth in busy loop Maarten Lankhorst
2026-06-15 20:18 ` [PATCH v8 18/27] drm/i915/gt: Fix selftests on PREEMPT_RT Maarten Lankhorst
2026-06-15 20:18 ` [PATCH v8 19/27] drm/i915/gt: Set stop_timeout() correctly on PREEMPT-RT Maarten Lankhorst
2026-06-15 20:18 ` [PATCH v8 20/27] drm/i915/display: Remove uncore lock from vlv_atomic_update_fifo Maarten Lankhorst
2026-06-15 20:36 ` sashiko-bot
2026-06-15 20:18 ` [PATCH v8 21/27] drm/i915: Use sleeping selftests for igt_atomic on PREEMPT_RT Maarten Lankhorst
2026-06-15 20:18 ` [PATCH v8 22/27] Revert "drm/i915: Depend on !PREEMPT_RT." Maarten Lankhorst
2026-06-15 20:18 ` [PATCH v8 23/27] PREEMPT_RT injection Maarten Lankhorst
2026-06-15 20:39 ` sashiko-bot
2026-06-15 20:18 ` [PATCH v8 24/27] FOR-CI: bump MAX_STACK_TRACE_ENTRIES Maarten Lankhorst
2026-06-15 20:35 ` sashiko-bot
2026-06-15 20:18 ` [PATCH v8 25/27] drm/i915/gt: Add a spinlock to prevent starvation of irq_work Maarten Lankhorst
2026-06-15 20:38 ` sashiko-bot
2026-06-15 20:18 ` [PATCH v8 26/27] drm/xe/display: Always use system memory on PREEMPT_RT for DPT Maarten Lankhorst
2026-06-15 20:39 ` sashiko-bot
2026-06-15 20:18 ` [PATCH v8 27/27] drm/xe/display: Prefer not to allocate a framebuffers in stolen memory Maarten Lankhorst
2026-06-15 20:41 ` sashiko-bot
2026-06-15 20:33 ` ✗ CI.checkpatch: warning for drm/i915/display: All patches to make PREEMPT_RT work on i915 + xe. (rev16) Patchwork
2026-06-15 20:34 ` ✓ CI.KUnit: success " Patchwork
2026-06-15 20:50 ` ✗ CI.checksparse: warning " Patchwork
2026-06-15 21:27 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-06-15 21:48 ` ✗ i915.CI.BAT: " Patchwork
2026-06-15 23:22 ` ✗ 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=20260615203240.0BEF61F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dev@lankhorst.se \
--cc=dri-devel@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.