public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
* [PATCH] drm/i915/audio: use generic_handle_irq_safe() for LPE audio irq
@ 2026-05-28 15:45 Runyu Xiao
  2026-05-29  7:48 ` Sebastian Andrzej Siewior
  2026-06-04  4:47 ` Claude review: " Claude Code Review Bot
  0 siblings, 2 replies; 10+ messages in thread
From: Runyu Xiao @ 2026-05-28 15:45 UTC (permalink / raw)
  To: jani.nikula, rodrigo.vivi
  Cc: joonas.lahtinen, tursulin, airlied, simona, bigeasy, clrkwllms,
	rostedt, jerome.anand, pierre-louis.bossart, tiwai, intel-gfx,
	intel-xe, dri-devel, linux-kernel, linux-rt-devel, runyu.xiao,
	jianhao.xu, stable

intel_lpe_audio_irq_handler() forwards the LPE audio child IRQ from the
i915 parent IRQ path with generic_handle_irq(). The forwarded child top
half is not an independent hardirq entry point; it inherits the context
of the outer i915 interrupt dispatch path.

This becomes a problem when the parent IRQ runs in threaded context, for
example on PREEMPT_RT or other forced-threading configurations. i915
requests the parent IRQ with IRQF_SHARED and without IRQF_NO_THREAD, so
the forwarded child handler can run with local IRQs enabled. That
violates the expected top-half execution semantics and can trigger an
"enabled interrupts" WARN.

The issue was identified on Linux v6.18.21 by our static analysis tool
and then manually reviewed on the i915 child-IRQ forwarding sites after
commit 8cadce97bf26 ("drm/i915/gsc: mei interrupt top half should be in
irq disabled context") fixed the same helper contract for the GSC path.

It was then validated with a reproducible QEMU no-device parent/child
IRQ harness that registers a threaded parent IRQ and a child IRQ
handler, then exercises both generic_handle_irq() and
generic_handle_irq_safe() under the same threaded parent context. In the
plain-helper phase, the child handler ran with irqs_disabled=0 and
triggered an "enabled interrupts" WARN. In the safe-helper phase, the
same child handler ran with irqs_disabled=1. This is family-level
runtime evidence for the same IRQ forwarding misuse pattern. No
Baytrail/Cherrytrail hardware was available to run the real i915 LPE
path end-to-end.

Use generic_handle_irq_safe() here so the forwarded LPE audio child IRQ
runs with local IRQs disabled even when the outer i915 dispatch path is
threaded.

Fixes: eef57324d926 ("drm/i915: setup bridge for HDMI LPE audio driver")
Cc: stable@vger.kernel.org
Signed-off-by: Runyu Xiao <runyu.xiao@seu.edu.cn>
---
 drivers/gpu/drm/i915/display/intel_lpe_audio.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/display/intel_lpe_audio.c b/drivers/gpu/drm/i915/display/intel_lpe_audio.c
index 42284e9928f2..ac1dfd592a9f 100644
--- a/drivers/gpu/drm/i915/display/intel_lpe_audio.c
+++ b/drivers/gpu/drm/i915/display/intel_lpe_audio.c
@@ -263,7 +263,7 @@ void intel_lpe_audio_irq_handler(struct intel_display *display)
 	if (!HAS_LPE_AUDIO(display))
 		return;
 
-	ret = generic_handle_irq(display->audio.lpe.irq);
+	ret = generic_handle_irq_safe(display->audio.lpe.irq);
 	if (ret)
 		drm_err_ratelimited(display->drm,
 				    "error handling LPE audio irq: %d\n", ret);
-- 
2.34.1

^ permalink raw reply related	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2026-06-04  4:47 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-28 15:45 [PATCH] drm/i915/audio: use generic_handle_irq_safe() for LPE audio irq Runyu Xiao
2026-05-29  7:48 ` Sebastian Andrzej Siewior
2026-05-29  9:50   ` Maarten Lankhorst
2026-05-29 12:21     ` Sebastian Andrzej Siewior
2026-05-29 14:25       ` Runyu Xiao
2026-05-29 15:21         ` Jani Nikula
2026-05-31 15:23           ` Runyu Xiao
2026-05-31 15:31             ` [PATCH v2] " Runyu Xiao
2026-06-01  9:04               ` Sebastian Andrzej Siewior
2026-06-04  4:47 ` Claude review: " Claude Code Review Bot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox