From: Fabio Estevam <festevam@gmail.com>
To: stable@vger.kernel.org
Cc: marc.zyngier@arm.com, Fabio Estevam <fabio.estevam@nxp.com>
Subject: [PATCH v2] irqchip/gic: Allow self-SGIs for SMP on UP configurations
Date: Fri, 9 Sep 2016 10:44:42 -0300 [thread overview]
Message-ID: <1473428682-14552-1-git-send-email-festevam@gmail.com> (raw)
From: Marc Zyngier <marc.zyngier@arm.com>
commit 059e232089e45b0befc9933d31209c225e08b426 upstream.
On systems where a single CPU is present, the GIC may not support
having SGIs delivered to a target list. In that case, we use the
self-SGI mechanism to allow the interrupt to be delivered locally.
Cc: <stable@vger.kernel.org> # 4.7.x
Tested-by: Fabio Estevam <fabio.estevam@nxp.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
---
Changes since v1:
- Add the 4.7.x notation
drivers/irqchip/irq-gic.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
index c2cab57..390fac5 100644
--- a/drivers/irqchip/irq-gic.c
+++ b/drivers/irqchip/irq-gic.c
@@ -769,6 +769,13 @@ static void gic_raise_softirq(const struct cpumask *mask, unsigned int irq)
int cpu;
unsigned long flags, map = 0;
+ if (unlikely(nr_cpu_ids == 1)) {
+ /* Only one CPU? let's do a self-IPI... */
+ writel_relaxed(2 << 24 | irq,
+ gic_data_dist_base(&gic_data[0]) + GIC_DIST_SOFTINT);
+ return;
+ }
+
raw_spin_lock_irqsave(&irq_controller_lock, flags);
/* Convert our logical CPU mask into a physical one. */
--
1.9.1
next reply other threads:[~2016-09-09 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 13:44 Fabio Estevam [this message]
2016-09-09 14:40 ` [PATCH v2] irqchip/gic: Allow self-SGIs for SMP on UP configurations Marc Zyngier
2016-09-09 15:31 ` Fabio Estevam
2016-09-09 15:42 ` Marc Zyngier
2016-09-09 15:48 ` Fabio Estevam
2016-09-09 16:06 ` Marc Zyngier
2016-09-09 16:12 ` Greg KH
2016-09-09 16:10 ` Greg KH
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=1473428682-14552-1-git-send-email-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=fabio.estevam@nxp.com \
--cc=marc.zyngier@arm.com \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.