From: Thomas Gleixner <tglx@linutronix.de>
To: Edgar Bonet <bonet@grenoble.cnrs.fr>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [ISSUE + PATCH] Interrupts were enabled early by spinlock guard
Date: Sat, 23 Aug 2025 21:33:48 +0200 [thread overview]
Message-ID: <877byt4yub.ffs@tglx> (raw)
In-Reply-To: <62be0896-6c90-4a27-81cb-7bd897d0e6f2@grenoble.cnrs.fr>
On Thu, Aug 14 2025 at 17:28, Edgar Bonet wrote:
>> I think the conversions in
>> drivers/irqchip/irq-atmel-aic.c:aic_irq_domain_xlate() and
>> drivers/irqchip/irq-loongson-liointc.c:liointc_set_type()
>> are also wrong, and need a similar change.
> The one in irq-atmel-aic.c looks indeed strikingly similar.
Yes. My bad.
I missed the fact, that this can be invoked during early boot when
interrupts are still disabled. After early boot they are always enabled
when xlate() is invoked.
> The one in irq-loongson-liointc.c is slightly different
> though. Instead of:
>
> irq_gc_lock_irqsave() -> guard(raw_spinlock_irq)
>
> it does:
>
> irq_gc_lock_irqsave() -> guard(raw_spinlock)
>
> I don't know what the implications are though.
That's in the set_type() callback which is always invoked with the
interrupt decriptor lock held and interrupts disabled, so doing the
'save/restore' dance there is pointless.
Can you send a patch for that atmel-aic thing too please?
Thanks,
tglx
next prev parent reply other threads:[~2025-08-23 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 12:59 [ISSUE + PATCH] Interrupts were enabled early by spinlock guard Edgar Bonet
2025-08-14 14:39 ` Geert Uytterhoeven
2025-08-14 15:28 ` Edgar Bonet
2025-08-23 19:33 ` Thomas Gleixner [this message]
2025-08-23 19:35 ` Thomas Gleixner
2025-08-25 12:35 ` Nicolas Ferre
2025-08-25 14:10 ` Nicolas Ferre
2025-08-25 12:33 ` Nicolas Ferre
2025-08-25 14:12 ` Nicolas Ferre
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=877byt4yub.ffs@tglx \
--to=tglx@linutronix.de \
--cc=alexandre.belloni@bootlin.com \
--cc=bonet@grenoble.cnrs.fr \
--cc=chenhuacai@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=geert@linux-m68k.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
/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