From: Leo Yan <leo.yan@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org
Cc: Leo Yan <leo.yan@linaro.org>, Orito Takao <orito.takao@socionext.com>
Subject: [RFC PATCH] irqchip/gic, gic-v3: Ensure data visibility in peripheral
Date: Wed, 1 Sep 2021 14:31:15 +0800 [thread overview]
Message-ID: <20210901063115.383026-1-leo.yan@linaro.org> (raw)
When an interrupt line is assered, GIC handles interrupt with the flow
(with EOImode == 1):
gic_handle_irq()
`> do_read_iar() => Change int state to active
`> gic_write_eoir() => Drop int priority
`> handle_domain_irq()
`> generic_handle_irq_desc()
`> handle_fasteoi_irq()
`> handle_irq_event() => Peripheral handler and
de-assert int line
`> cond_unmask_eoi_irq()
`> chip->irq_eoi()
`> gic_eoimode1_eoi_irq() => Change int state to inactive
In this flow, it has no explicit memory barrier between the functions
handle_irq_event() and chip->irq_eoi(), it's possible that the
outstanding data has not reached device in handle_irq_event() but the
callback chip->irq_eoi() is invoked, this can lead to state transition
for level triggered interrupt:
Flow | Interrupt state in GIC
---------------------------------+-------------------------------------
Interrupt line is asserted | 'inactive' -> 'pending'
do_read_iar() | 'pending' -> 'pending & active'
handle_irq_event() | Write peripheral register but it's
| not visible for device, so the
| interrupt line is still asserted
chip->irq_eoi() | 'pending & active' -> 'pending'
...
Produce spurious interrupt |
with interrupt ID: 1024 |
| Finally the peripheral reigster is
| updated and the interrupt line is
| deasserted: 'pending' -> 'inactive'
To avoid this potential issue, this patch adds wmb() barrier prior to
invoke EOI operation, this can make sure the interrupt line is
de-asserted in peripheral before deactivating interrupt in GIC. At the
end, this can avoid spurious interrupt.
Reported-by: Orito Takao <orito.takao@socionext.com>
Signed-off-by: Leo Yan <leo.yan@linaro.org>
---
drivers/irqchip/irq-gic-v3.c | 4 ++++
drivers/irqchip/irq-gic.c | 4 ++++
2 files changed, 8 insertions(+)
diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c
index e0f4debe64e1..fcd1477e2274 100644
--- a/drivers/irqchip/irq-gic-v3.c
+++ b/drivers/irqchip/irq-gic-v3.c
@@ -530,6 +530,8 @@ static void gic_irq_nmi_teardown(struct irq_data *d)
static void gic_eoi_irq(struct irq_data *d)
{
+ /* Ensure the data is written to peripheral */
+ wmb();
gic_write_eoir(gic_irq(d));
}
@@ -541,6 +543,8 @@ static void gic_eoimode1_eoi_irq(struct irq_data *d)
*/
if (gic_irq(d) >= 8192 || irqd_is_forwarded_to_vcpu(d))
return;
+ /* Ensure the data is written to peripheral */
+ wmb();
gic_write_dir(gic_irq(d));
}
diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
index d329ec3d64d8..3e9d4b6dc31b 100644
--- a/drivers/irqchip/irq-gic.c
+++ b/drivers/irqchip/irq-gic.c
@@ -222,6 +222,8 @@ static void gic_eoi_irq(struct irq_data *d)
if (hwirq < 16)
hwirq = this_cpu_read(sgi_intid);
+ /* Ensure the data is written to peripheral */
+ wmb();
writel_relaxed(hwirq, gic_cpu_base(d) + GIC_CPU_EOI);
}
@@ -236,6 +238,8 @@ static void gic_eoimode1_eoi_irq(struct irq_data *d)
if (hwirq < 16)
hwirq = this_cpu_read(sgi_intid);
+ /* Ensure the data is written to peripheral */
+ wmb();
writel_relaxed(hwirq, gic_cpu_base(d) + GIC_CPU_DEACTIVATE);
}
--
2.25.1
next reply other threads:[~2021-09-01 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 6:31 Leo Yan [this message]
2021-09-01 7:03 ` Marc Zyngier
2021-09-01 7:27 ` Leo Yan
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=20210901063115.383026-1-leo.yan@linaro.org \
--to=leo.yan@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=orito.takao@socionext.com \
--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
all inboxes | Powered by JetHome®