From: Marc Zyngier <maz@kernel.org>
To: Anup Patel <apatel@ventanamicro.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Thomas Gleixner <tglx@linutronix.de>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Atish Patra <atishp@atishpatra.org>,
Alistair Francis <Alistair.Francis@wdc.com>,
Anup Patel <anup@brainfault.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Bin Meng <bmeng.cn@gmail.com>
Subject: Re: [PATCH v9 1/7] RISC-V: Clear SIP bit only when using SBI IPI operations
Date: Thu, 08 Sep 2022 09:38:36 +0100 [thread overview]
Message-ID: <87czc6uupf.wl-maz@kernel.org> (raw)
In-Reply-To: <20220903161309.32848-2-apatel@ventanamicro.com>
On Sat, 03 Sep 2022 17:13:03 +0100,
Anup Patel <apatel@ventanamicro.com> wrote:
>
> 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>
> ---
> 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 775d3322b422..fc614650a2e3 100644
> --- a/arch/riscv/kernel/sbi.c
> +++ b/arch/riscv/kernel/sbi.c
> @@ -643,8 +643,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 760a64518c58..c56d67f53ea9 100644
> --- a/arch/riscv/kernel/smp.c
> +++ b/arch/riscv/kernel/smp.c
> @@ -83,8 +83,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);
This really begs the question: why on Earth are these things exported
to *modules*? I cannot see a good reason why they should be...
M>
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-09-08 8:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 16:13 [PATCH v9 0/7] RISC-V IPI Improvements Anup Patel
2022-09-03 16:13 ` [PATCH v9 1/7] RISC-V: Clear SIP bit only when using SBI IPI operations Anup Patel
2022-09-03 20:16 ` Jessica Clarke
2022-09-04 4:39 ` Anup Patel
2022-09-04 21:45 ` Jessica Clarke
2022-09-07 23:18 ` Atish Patra
2022-09-08 8:38 ` Marc Zyngier [this message]
2022-09-08 12:37 ` Anup Patel
2022-09-03 16:13 ` [PATCH v9 2/7] irqchip/riscv-intc: Allow drivers to directly discover INTC hwnode Anup Patel
2022-09-07 23:20 ` Atish Patra
2022-09-03 16:13 ` [PATCH v9 3/7] genirq: Add mechanism to multiplex a single HW IPI Anup Patel
2022-09-21 18:29 ` Marc Zyngier
2022-11-01 10:18 ` Anup Patel
[not found] ` <20220904080601.2405-1-hdanton@sina.com>
2022-11-14 8:56 ` Anup Patel
2022-09-03 16:13 ` [PATCH v9 4/7] RISC-V: Treat IPIs as normal Linux IRQs Anup Patel
2022-09-03 16:13 ` [PATCH v9 5/7] RISC-V: Allow marking IPIs as suitable for remote FENCEs Anup Patel
2022-09-03 16:13 ` [PATCH v9 6/7] RISC-V: Use IPIs for remote TLB flush when possible Anup Patel
2022-09-03 16:13 ` [PATCH v9 7/7] RISC-V: Use IPIs for remote icache " Anup Patel
2022-09-21 11:47 ` [PATCH v9 0/7] RISC-V IPI Improvements Anup Patel
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=87czc6uupf.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Alistair.Francis@wdc.com \
--cc=anup@brainfault.org \
--cc=apatel@ventanamicro.com \
--cc=atishp@atishpatra.org \
--cc=bmeng.cn@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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