public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: andre.przywara@arm.com (Andre Przywara)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] irqchip/gic-v3-its: bail out on already enabled LPIs
Date: Thu, 16 Mar 2017 17:05:41 +0000	[thread overview]
Message-ID: <20170316170542.3568-2-andre.przywara@arm.com> (raw)
In-Reply-To: <20170316170542.3568-1-andre.przywara@arm.com>

The GICv3 spec says that once LPIs have been enabled, they can't be
disabled anymore:
"When a write changes this bit from 0 to 1, this bit becomes RES1 ..."
As we can't setup the pending and property table registers when LPIs are
enabled, we have to bail out here in this case.
But first try to disable LPIs anyway, to check whether this actually works.
If not, return an error.

Signed-off-by: Andre Przywara <andre.przywara@arm.com>
---
 drivers/irqchip/irq-gic-v3-its.c | 36 ++++++++++++++++++++++++++++--------
 1 file changed, 28 insertions(+), 8 deletions(-)

diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
index f77f840..b777c57 100644
--- a/drivers/irqchip/irq-gic-v3-its.c
+++ b/drivers/irqchip/irq-gic-v3-its.c
@@ -1082,12 +1082,30 @@ static int its_alloc_collections(struct its_node *its)
 	return 0;
 }
 
-static void its_cpu_init_lpis(void)
+static int its_cpu_init_lpis(void)
 {
 	void __iomem *rbase = gic_data_rdist_rd_base();
 	struct page *pend_page;
 	u64 val, tmp;
 
+	/*
+	 * Architecturally, once LPIs have been enabled on a specific
+	 * redistributor, they can't be disabled anymore (the enable
+	 * bit becomes RES1).
+	 * But as we can't setup the pending and property table registers
+	 * while LPIs are enabled, we are basically screwed in this case.
+	 * But be slightly more optimistic here, and actually check whether
+	 * this is really implemented like this.
+	 */
+	val = readl_relaxed(rbase + GICR_CTLR);
+	val &= ~GICR_CTLR_ENABLE_LPIS;
+	writel_relaxed(val, rbase + GICR_CTLR);
+	if (readl_relaxed(rbase + GICR_CTLR) & GICR_CTLR_ENABLE_LPIS) {
+		pr_warn("CPU%d: LPIs already enabled, cannot initialize redistributor\n",
+			smp_processor_id());
+		return -EBUSY;
+	}
+
 	/* If we didn't allocate the pending table yet, do it now */
 	pend_page = gic_data_rdist()->pend_page;
 	if (!pend_page) {
@@ -1101,7 +1119,7 @@ static void its_cpu_init_lpis(void)
 		if (!pend_page) {
 			pr_err("Failed to allocate PENDBASE for CPU%d\n",
 			       smp_processor_id());
-			return;
+			return -ENOMEM;
 		}
 
 		/* Make sure the GIC will observe the zero-ed page */
@@ -1113,11 +1131,6 @@ static void its_cpu_init_lpis(void)
 		gic_data_rdist()->pend_page = pend_page;
 	}
 
-	/* Disable LPIs */
-	val = readl_relaxed(rbase + GICR_CTLR);
-	val &= ~GICR_CTLR_ENABLE_LPIS;
-	writel_relaxed(val, rbase + GICR_CTLR);
-
 	/*
 	 * Make sure any change to the table is observable by the GIC.
 	 */
@@ -1174,6 +1187,8 @@ static void its_cpu_init_lpis(void)
 
 	/* Make sure the GIC has seen the above */
 	dsb(sy);
+
+	return 0;
 }
 
 static void its_cpu_init_collection(void)
@@ -1789,12 +1804,17 @@ static bool gic_rdists_supports_plpis(void)
 
 int its_cpu_init(void)
 {
+	int ret;
+
 	if (!list_empty(&its_nodes)) {
 		if (!gic_rdists_supports_plpis()) {
 			pr_info("CPU%d: LPIs not supported\n", smp_processor_id());
 			return -ENXIO;
 		}
-		its_cpu_init_lpis();
+		ret = its_cpu_init_lpis();
+		if (ret)
+			return ret;
+
 		its_cpu_init_collection();
 	}
 
-- 
2.9.0

  reply	other threads:[~2017-03-16 17:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 17:05 [PATCH 0/2] irqchip/gic-v3-its: LPI tables fixes Andre Przywara
2017-03-16 17:05 ` Andre Przywara [this message]
2017-03-16 17:25   ` [PATCH 1/2] irqchip/gic-v3-its: bail out on already enabled LPIs Shanker Donthineni
2017-03-17  9:46     ` Marc Zyngier
2017-03-17 10:43       ` Shanker Donthineni
2017-03-17 11:01         ` Marc Zyngier
2017-03-16 17:05 ` [PATCH 2/2] irqchip/gic-v3-its: always check for cacheability attributes Andre Przywara

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=20170316170542.3568-2-andre.przywara@arm.com \
    --to=andre.przywara@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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