From: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, benh@kernel.crashing.org, clg@kaod.org
Cc: andrew.donnellan@au1.ibm.com, vaibhav@linux.vnet.ibm.com
Subject: [RFC] powerpc/xive: Remove irq from queue when it is shutdown
Date: Wed, 14 Mar 2018 17:58:08 +0100 [thread overview]
Message-ID: <20180314165808.26628-1-fbarrat@linux.vnet.ibm.com> (raw)
If a driver has called free_irq() but an irq is waiting in a queue, an
error is logged when a cpu processes it:
irq 232, desc: 0000000044e5941a, depth: 1, count: 9823, unhandled: 0
->handle_irq(): 0000000023f2e352,
handle_bad_irq+0x0/0x2e0
->irq_data.chip(): 000000007fd7bf50,
no_irq_chip+0x0/0x110
->action(): (null)
IRQ_NOREQUEST set
unexpected IRQ trap at vector e8
In most cases, it's due to a driver bug or a misbehaving device, but
it can be observed with opencapi with no involvment of a device. AFU
interrupts are triggered by writing a special page of a process, but
it's possible for a thread of that process to write to that page as
well. If that process exits abruptly, the driver will free the AFU
interrupts resources, but there's no possible quiescing of the
process, so we may have interrupts in the queue.
This patch adds a scan of the queue when an interrupt is shutdown to
replace any pending irq with XIVE_BAD_IRQ, since those are ignored.
Also move when XIVE_BAD_IRQs are ignored closer to reading the queue,
so that we can reset the CPPR if it's the last interrupt in the queue.
Signed-off-by: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
---
arch/powerpc/sysdev/xive/common.c | 69 ++++++++++++++++++++++++++++++++++++---
1 file changed, 65 insertions(+), 4 deletions(-)
diff --git a/arch/powerpc/sysdev/xive/common.c b/arch/powerpc/sysdev/xive/common.c
index 3459015092fa..91047bc7c731 100644
--- a/arch/powerpc/sysdev/xive/common.c
+++ b/arch/powerpc/sysdev/xive/common.c
@@ -148,8 +148,16 @@ static u32 xive_scan_interrupts(struct xive_cpu *xc, bool just_peek)
prio = ffs(xc->pending_prio) - 1;
DBG_VERBOSE("scan_irq: trying prio %d\n", prio);
- /* Try to fetch */
- irq = xive_read_eq(&xc->queue[prio], just_peek);
+ /*
+ * Try to fetch.
+ * When not peeking, drop any BAD_IRQ on the floor
+ * now. If we let it reach get_irq() and it's the last
+ * one, then we'd need to rescan again to reset the
+ * CPPR
+ */
+ do {
+ irq = xive_read_eq(&xc->queue[prio], just_peek);
+ } while (irq == XIVE_BAD_IRQ && !just_peek);
/* Found something ? That's it */
if (irq)
@@ -282,8 +290,6 @@ static unsigned int xive_get_irq(void)
irq, xc->pending_prio);
/* Return pending interrupt if any */
- if (irq == XIVE_BAD_IRQ)
- return 0;
return irq;
}
@@ -592,6 +598,58 @@ static unsigned int xive_irq_startup(struct irq_data *d)
return 0;
}
+static void xive_remove_from_queue(unsigned int hw_irq, int cpu)
+{
+ struct xive_cpu *xc;
+ struct xive_q *q;
+ u32 irq = 0, cur, idx, toggle, prev;
+ u8 prio;
+ int count;
+
+ xc = per_cpu(xive_cpu, cpu);
+
+ /*
+ * Only one queue is really in use, but let's try stay generic, and
+ * check all of them
+ */
+ for (prio = 0; prio < XIVE_MAX_QUEUES; prio++) {
+ q = &xc->queue[prio];
+ if (!q->qpage)
+ continue;
+
+ /*
+ * We can't read a reliable index and toggle without
+ * locking, as another cpu can process an interrupt
+ * and read the queue at any given time. So use the
+ * toggle from the previous index, which should be ok
+ * as long as the queue doesn't overflow.
+ */
+ idx = q->idx;
+ prev = (idx - 1) & q->msk;
+ cur = be32_to_cpup(q->qpage + prev);
+ toggle = (cur >> 31) ^ 1;
+ count = 0;
+ do {
+ count++;
+ cur = be32_to_cpup(q->qpage + idx);
+ if ((cur >> 31) == toggle)
+ irq = 0;
+ else
+ irq = cur & 0x7fffffff;
+
+ if (irq == hw_irq) {
+ cur &= 1 << 31;
+ cur |= XIVE_BAD_IRQ;
+ *(q->qpage + idx) = cpu_to_be32(cur);
+ }
+
+ idx = (idx + 1) & q->msk;
+ if (idx == 0)
+ toggle ^= 1;
+ } while (irq && (count < q->msk));
+ }
+}
+
static void xive_irq_shutdown(struct irq_data *d)
{
struct xive_irq_data *xd = irq_data_get_irq_handler_data(d);
@@ -624,6 +682,9 @@ static void xive_irq_shutdown(struct irq_data *d)
get_hard_smp_processor_id(xd->target),
0xff, XIVE_BAD_IRQ);
+ /* configure_irq() syncs the queue */
+ xive_remove_from_queue(hw_irq, xd->target);
+
xive_dec_target_count(xd->target);
xd->target = XIVE_INVALID_TARGET;
}
--
2.14.1
next reply other threads:[~2018-03-14 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 16:58 Frederic Barrat [this message]
2018-03-14 17:47 ` [RFC] powerpc/xive: Remove irq from queue when it is shutdown Cédric Le Goater
2018-03-15 22:56 ` Benjamin Herrenschmidt
2018-03-15 22:59 ` Benjamin Herrenschmidt
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=20180314165808.26628-1-fbarrat@linux.vnet.ibm.com \
--to=fbarrat@linux.vnet.ibm.com \
--cc=andrew.donnellan@au1.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=clg@kaod.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=vaibhav@linux.vnet.ibm.com \
/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).