From: "irqchip-bot for Anup Patel" <tip-bot2@linutronix.de>
To: linux-kernel@vger.kernel.org
Cc: Anup Patel <apatel@ventanamicro.com>,
Bin Meng <bmeng.cn@gmail.com>, Atish Patra <atishp@rivosinc.com>,
Palmer Dabbelt <palmer@rivosinc.com>,
Marc Zyngier <maz@kernel.org>,
tglx@linutronix.de
Subject: [irqchip: irq/irqchip-next] RISC-V: Clear SIP bit only when using SBI IPI operations
Date: Sat, 08 Apr 2023 10:45:19 -0000 [thread overview]
Message-ID: <168095071929.404.14218576691551578438.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20230328035223.1480939-2-apatel@ventanamicro.com>
The following commit has been merged into the irq/irqchip-next branch of irqchip:
Commit-ID: 3ee92565b83ecc08e5b0c878dd87a2973eaca2ea
Gitweb: https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms/3ee92565b83ecc08e5b0c878dd87a2973eaca2ea
Author: Anup Patel <apatel@ventanamicro.com>
AuthorDate: Tue, 28 Mar 2023 09:22:17 +05:30
Committer: Marc Zyngier <maz@kernel.org>
CommitterDate: Sat, 08 Apr 2023 11:26:23 +01:00
RISC-V: Clear SIP bit only when using SBI IPI operations
The software interrupt pending (i.e. [M|S]SIP) bit is writeable for
S-mode but read-only for M-mode so we clear this bit only when using
SBI IPI operations.
Signed-off-by: Anup Patel <apatel@ventanamicro.com>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Atish Patra <atishp@rivosinc.com>
Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20230328035223.1480939-2-apatel@ventanamicro.com
---
arch/riscv/kernel/sbi.c | 8 +++++++-
arch/riscv/kernel/smp.c | 2 --
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/arch/riscv/kernel/sbi.c b/arch/riscv/kernel/sbi.c
index 5c87db8..ac99a70 100644
--- a/arch/riscv/kernel/sbi.c
+++ b/arch/riscv/kernel/sbi.c
@@ -646,8 +646,14 @@ static void sbi_send_cpumask_ipi(const struct cpumask *target)
sbi_send_ipi(target);
}
+static void sbi_ipi_clear(void)
+{
+ csr_clear(CSR_IP, IE_SIE);
+}
+
static const struct riscv_ipi_ops sbi_ipi_ops = {
- .ipi_inject = sbi_send_cpumask_ipi
+ .ipi_inject = sbi_send_cpumask_ipi,
+ .ipi_clear = sbi_ipi_clear
};
void __init sbi_init(void)
diff --git a/arch/riscv/kernel/smp.c b/arch/riscv/kernel/smp.c
index 8c3b59f..8a12768 100644
--- a/arch/riscv/kernel/smp.c
+++ b/arch/riscv/kernel/smp.c
@@ -112,8 +112,6 @@ void riscv_clear_ipi(void)
{
if (ipi_ops && ipi_ops->ipi_clear)
ipi_ops->ipi_clear();
-
- csr_clear(CSR_IP, IE_SIE);
}
EXPORT_SYMBOL_GPL(riscv_clear_ipi);
next prev parent reply other threads:[~2023-04-08 10:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 3:52 [PATCH v18 0/7] RISC-V IPI Improvements Anup Patel
2023-03-28 3:52 ` [PATCH v18 1/7] RISC-V: Clear SIP bit only when using SBI IPI operations Anup Patel
2023-04-08 10:45 ` irqchip-bot for Anup Patel [this message]
2023-03-28 3:52 ` [PATCH v18 2/7] irqchip/riscv-intc: Allow drivers to directly discover INTC hwnode Anup Patel
2023-04-08 10:45 ` [irqchip: irq/irqchip-next] " irqchip-bot for Anup Patel
2023-03-28 3:52 ` [PATCH v18 3/7] RISC-V: Treat IPIs as normal Linux IRQs Anup Patel
2023-04-08 10:45 ` [irqchip: irq/irqchip-next] " irqchip-bot for Anup Patel
2023-03-28 3:52 ` [PATCH v18 4/7] RISC-V: Allow marking IPIs as suitable for remote FENCEs Anup Patel
2023-04-08 10:45 ` [irqchip: irq/irqchip-next] " irqchip-bot for Anup Patel
2023-03-28 3:52 ` [PATCH v18 5/7] RISC-V: Use IPIs for remote TLB flush when possible Anup Patel
2023-04-08 10:45 ` [irqchip: irq/irqchip-next] " irqchip-bot for Anup Patel
2023-03-28 3:52 ` [PATCH v18 6/7] RISC-V: Use IPIs for remote icache " Anup Patel
2023-04-08 10:45 ` [irqchip: irq/irqchip-next] " irqchip-bot for Anup Patel
2023-03-28 3:52 ` [PATCH v18 7/7] irqchip/riscv-intc: Add empty irq_eoi() for chained irq handlers Anup Patel
2023-04-08 10:45 ` [irqchip: irq/irqchip-next] " irqchip-bot for Anup Patel
2023-03-28 3:56 ` [PATCH v18 0/7] RISC-V IPI Improvements Anup Patel
2023-05-08 14:41 ` patchwork-bot+linux-riscv
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=168095071929.404.14218576691551578438.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=apatel@ventanamicro.com \
--cc=atishp@rivosinc.com \
--cc=bmeng.cn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=palmer@rivosinc.com \
--cc=tglx@linutronix.de \
/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®