From: Marc Zyngier <maz@kernel.org>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: daniel.thompson@linaro.org, jason@lakedaemon.net,
catalin.marinas@arm.com, dianders@chromium.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, jason.wessel@windriver.com,
kgdb-bugreport@lists.sourceforge.net, tglx@linutronix.de,
will@kernel.org, julien.thierry.kdev@gmail.com
Subject: Re: [RFC Patch v1 2/4] irqchip/gic-v3: Add support to handle SGI as pseudo NMI
Date: Sat, 25 Apr 2020 11:29:50 +0100 [thread overview]
Message-ID: <20200425112950.3a4815b6@why> (raw)
In-Reply-To: <1587726554-32018-3-git-send-email-sumit.garg@linaro.org>
On Fri, 24 Apr 2020 16:39:12 +0530
Sumit Garg <sumit.garg@linaro.org> wrote:
Hi Sumit,
> With pseudo NMIs enabled, interrupt controller can be configured to
> deliver SGI as a pseudo NMI. So add corresponding handling for SGIs.
>
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
> ---
> drivers/irqchip/irq-gic-v3.c | 22 +++++++++++++++++-----
> 1 file changed, 17 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c
> index d7006ef..be361bf 100644
> --- a/drivers/irqchip/irq-gic-v3.c
> +++ b/drivers/irqchip/irq-gic-v3.c
> @@ -609,17 +609,29 @@ static inline void gic_handle_nmi(u32 irqnr, struct pt_regs *regs)
> if (irqs_enabled)
> nmi_enter();
>
> - if (static_branch_likely(&supports_deactivate_key))
> - gic_write_eoir(irqnr);
> /*
> * Leave the PSR.I bit set to prevent other NMIs to be
> * received while handling this one.
> * PSR.I will be restored when we ERET to the
> * interrupted context.
> */
> - err = handle_domain_nmi(gic_data.domain, irqnr, regs);
> - if (err)
> - gic_deactivate_unhandled(irqnr);
> + if (likely(irqnr > 15)) {
> + if (static_branch_likely(&supports_deactivate_key))
> + gic_write_eoir(irqnr);
> +
> + err = handle_domain_nmi(gic_data.domain, irqnr, regs);
> + if (err)
> + gic_deactivate_unhandled(irqnr);
> + } else {
> + gic_write_eoir(irqnr);
> + if (static_branch_likely(&supports_deactivate_key))
> + gic_write_dir(irqnr);
> +#ifdef CONFIG_SMP
> + handle_IPI(irqnr, regs);
> +#else
> + WARN_ONCE(true, "Unexpected SGI received!\n");
> +#endif
> + }
>
> if (irqs_enabled)
> nmi_exit();
If there is one thing I would like to avoid, it is to add more ugly
hacks to the way we handle SGIs. There is very little reason why SGIs
should be handled differently from all other interrupts. They have the
same properties, and it is only because of the 32bit legacy that we deal
with them in such a cumbersome way. Nothing that we cannot fix though.
What I would really like to see is first a conversion of the SGIs to
normal, full fat interrupts. These interrupts can then be configured as
NMI using the normal API.
I think Julien had something along these lines (or was that limited to
the PMU?). Otherwise, I'll happily help you with that.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-04-25 10:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 11:09 [RFC Patch v1 0/4] arm64: Introduce new IPI as IPI_CALL_NMI_FUNC Sumit Garg
2020-04-24 11:09 ` [RFC Patch v1 1/4] arm64: smp: Introduce a " Sumit Garg
2020-04-24 11:09 ` [RFC Patch v1 2/4] irqchip/gic-v3: Add support to handle SGI as pseudo NMI Sumit Garg
2020-04-25 10:29 ` Marc Zyngier [this message]
2020-04-25 14:32 ` Marc Zyngier
2020-04-28 14:11 ` Sumit Garg
2020-04-29 8:23 ` Marc Zyngier
2020-04-30 7:20 ` Sumit Garg
2020-04-30 9:13 ` Marc Zyngier
2020-04-30 12:13 ` Sumit Garg
2020-05-01 13:03 ` Sumit Garg
2020-05-05 4:09 ` Sumit Garg
2020-05-05 10:08 ` Marc Zyngier
2020-05-05 11:33 ` Sumit Garg
2020-05-13 10:02 ` Sumit Garg
2020-05-19 14:51 ` Marc Zyngier
2020-04-24 11:09 ` [RFC Patch v1 3/4] irqchip/gic-v3: Enable arch specific IPI " Sumit Garg
2020-04-24 11:09 ` [RFC Patch v1 4/4] arm64: kgdb: Round up cpus using IPI_CALL_NMI_FUNC Sumit Garg
2020-04-24 20:46 ` Doug Anderson
2020-04-27 4:52 ` Sumit Garg
2020-04-24 20:49 ` [RFC Patch v1 0/4] arm64: Introduce new IPI as IPI_CALL_NMI_FUNC Doug Anderson
2020-04-27 4:54 ` Sumit Garg
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=20200425112950.3a4815b6@why \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=jason@lakedaemon.net \
--cc=julien.thierry.kdev@gmail.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sumit.garg@linaro.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).