public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
* [PATCH 0/2] MEI interrupt fixes
@ 2026-03-17 13:47 Simon Richter
  2026-03-17 13:47 ` [PATCH 1/2] drm/xe: allow request_irq on GSC interrupt Simon Richter
                   ` (5 more replies)
  0 siblings, 6 replies; 8+ messages in thread
From: Simon Richter @ 2026-03-17 13:47 UTC (permalink / raw)
  To: intel-xe, dri-devel; +Cc: Simon Richter

Hi,

the MEI softirq does not use an irq domain, so the NUMA node cannot be
inferred from the node of the controller, and the map function does not
automatically clear the IRQ_NOREQUEST flag.

On x86, the IRQ_NOREQUEST flag is not set by platform code on allocation,
but that appears to be an oversight; other platforms set it on allocation,
and expect either irq_domain_associate_locked() or the device setup code to
clear it.

The flags are probably worth backporting (without that patch, the GSC is
unavailable because request_irq() fails), the NUMA patch is probably not
important enough (but doesn't hurt either).

   Simon

Simon Richter (2):
  drm/xe: allow request_irq on GSC interrupt
  drm/xe: Use same NUMA node for MEI interrupt

 drivers/gpu/drm/xe/xe_heci_gsc.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

-- 
2.47.3


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

end of thread, other threads:[~2026-03-18 23:42 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-03-17 13:47 [PATCH 0/2] MEI interrupt fixes Simon Richter
2026-03-17 13:47 ` [PATCH 1/2] drm/xe: allow request_irq on GSC interrupt Simon Richter
2026-03-17 14:52   ` Greg KH
2026-03-17 13:47 ` [PATCH 2/2] drm/xe: Use same NUMA node for MEI interrupt Simon Richter
2026-03-17 13:52 ` ✗ CI.checkpatch: warning for MEI interrupt fixes Patchwork
2026-03-17 13:54 ` ✓ CI.KUnit: success " Patchwork
2026-03-17 14:41 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-18 23:42 ` ✗ Xe.CI.FULL: " Patchwork

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