Thread (26 messages) 26 messages, 4 authors, 2021-02-24

Re: [PATCH 5/8] arm64: irq: add a default handle_irq panic function

From: Marc Zyngier <maz@kernel.org>
Date: 2021-02-22 12:56:47
Also in: lkml

On Mon, 22 Feb 2021 12:06:14 +0000,
Mark Rutland [off-list ref] wrote:
On Mon, Feb 22, 2021 at 11:43:13AM +0000, Marc Zyngier wrote:
[...]
quoted
As I said, it's not a big deal. I doubt that we'll see default_handle_irq()
exploding in practice. But the real nit here is the difference of treatment
between IRQ and FIQ. *IF* we ever get a system that only signals its
interrupt as FIQ (and I don't see why we'd forbid that), then we would
That's a fair point.

For consistency, we could remove the init_IRQ() panic() and instead log
the registered handlers, e.g.

| pr_info("Root IRQ handler is %ps\n", handle_arch_irq);
| pr_info("Root FIQ handler is %ps\n", handle_arch_fiq);

... or do that inside the set_handle_{irq,fiq}() functions. That way the
messages (or absence thereof) would be sufficient to diagnose the lack
of a root IRQ/FIQ handler when IRQ/FIQ happens to be quiescent.

Does that sound any better?
Yup, I quite like the second variant (using set_handle_{irq,fiq}()).

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help