mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Jiangshan Yi <yijiangshan@kylinos.cn>
Cc: lpieralisi@kernel.org, tglx@kernel.org, radu@rendec.net,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, 13667453960@163.com
Subject: Re: [PATCH v2] irqchip/gic-v5: Install root IRQ handler last in gicv5_init_common()
Date: Fri, 04 Sep 2026 08:39:47 +0100	[thread overview]
Message-ID: <86mrtx4g8s.wl-maz@kernel.org> (raw)
In-Reply-To: <20260903104014.587068-1-yijiangshan@kylinos.cn>

On Thu, 03 Sep 2026 11:40:14 +0100,
Jiangshan Yi <yijiangshan@kylinos.cn> wrote:
> 
> set_handle_irq() cannot be undone: once a handler is installed, any
> further call returns -EBUSY, so the set_handle_irq(NULL) in the error
> path has never worked.  Drop it, and install the root handler only
> after gicv5_irs_enable() has succeeded.
> 
> set_handle_irq() only fails if another root handler is already
> installed, which cannot happen on a GICv5 system.  Should it ever
> fail, the system is unusable: panic instead of unwinding.

Note that the system is dead either way, as it isn't like someone is
going to provide a replacement interrupt controller when GICv5 fails.
So any error in this function is pretty fatal for the whole system.

That said, this is still a reasonable cleanup.

> 
> Link: https://lore.kernel.org/r/87fqzrmywu.wl-maz@kernel.org
> Signed-off-by: Jiangshan Yi <yijiangshan@kylinos.cn>

Reviewed-by: Marc Zyngier <maz@kernel.org>

	M.

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

  parent reply	other threads:[~2026-09-04  7:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 10:40 Jiangshan Yi
2026-09-03 11:09 ` Lorenzo Pieralisi
2026-09-04  7:39 ` Marc Zyngier [this message]
2026-09-04 13:40 ` [tip: irq/drivers] " tip-bot2 for Jiangshan Yi

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=86mrtx4g8s.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=13667453960@163.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=radu@rendec.net \
    --cc=tglx@kernel.org \
    --cc=yijiangshan@kylinos.cn \
    /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

all inboxes | Powered by JetHome®