From: patchwork-bot+linux-riscv@kernel.org
To: Anup Patel <apatel@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, tglx@linutronix.de, maz@kernel.org,
daniel.lezcano@linaro.org, atishp@atishpatra.org,
Alistair.Francis@wdc.com, anup@brainfault.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v18 0/7] RISC-V IPI Improvements
Date: Mon, 08 May 2023 14:41:56 +0000 [thread overview]
Message-ID: <168355691627.25692.3962222758677102007.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230328035223.1480939-1-apatel@ventanamicro.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Marc Zyngier <maz@kernel.org>:
On Tue, 28 Mar 2023 09:22:16 +0530 you wrote:
> This series aims to improve IPI support in Linux RISC-V in following ways:
> 1) Treat IPIs as normal per-CPU interrupts instead of having custom RISC-V
> specific hooks. This also makes Linux RISC-V IPI support aligned with
> other architectures.
> 2) Remote TLB flushes and icache flushes should prefer local IPIs instead
> of SBI calls whenever we have specialized hardware (such as RISC-V AIA
> IMSIC and RISC-V SWI) which allows S-mode software to directly inject
> IPIs without any assistance from M-mode runtime firmware.
>
> [...]
Here is the summary with links:
- [v18,1/7] RISC-V: Clear SIP bit only when using SBI IPI operations
https://git.kernel.org/riscv/c/3ee92565b83e
- [v18,2/7] irqchip/riscv-intc: Allow drivers to directly discover INTC hwnode
https://git.kernel.org/riscv/c/0c60a31ce62c
- [v18,3/7] RISC-V: Treat IPIs as normal Linux IRQs
https://git.kernel.org/riscv/c/832f15f42646
- [v18,4/7] RISC-V: Allow marking IPIs as suitable for remote FENCEs
https://git.kernel.org/riscv/c/fb0f3d281b7f
- [v18,5/7] RISC-V: Use IPIs for remote TLB flush when possible
https://git.kernel.org/riscv/c/18d2199d8105
- [v18,6/7] RISC-V: Use IPIs for remote icache flush when possible
https://git.kernel.org/riscv/c/627922843235
- [v18,7/7] irqchip/riscv-intc: Add empty irq_eoi() for chained irq handlers
https://git.kernel.org/riscv/c/f8415f2def18
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Anup Patel <apatel@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, tglx@linutronix.de, maz@kernel.org,
daniel.lezcano@linaro.org, atishp@atishpatra.org,
Alistair.Francis@wdc.com, anup@brainfault.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v18 0/7] RISC-V IPI Improvements
Date: Mon, 08 May 2023 14:41:56 +0000 [thread overview]
Message-ID: <168355691627.25692.3962222758677102007.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230328035223.1480939-1-apatel@ventanamicro.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Marc Zyngier <maz@kernel.org>:
On Tue, 28 Mar 2023 09:22:16 +0530 you wrote:
> This series aims to improve IPI support in Linux RISC-V in following ways:
> 1) Treat IPIs as normal per-CPU interrupts instead of having custom RISC-V
> specific hooks. This also makes Linux RISC-V IPI support aligned with
> other architectures.
> 2) Remote TLB flushes and icache flushes should prefer local IPIs instead
> of SBI calls whenever we have specialized hardware (such as RISC-V AIA
> IMSIC and RISC-V SWI) which allows S-mode software to directly inject
> IPIs without any assistance from M-mode runtime firmware.
>
> [...]
Here is the summary with links:
- [v18,1/7] RISC-V: Clear SIP bit only when using SBI IPI operations
https://git.kernel.org/riscv/c/3ee92565b83e
- [v18,2/7] irqchip/riscv-intc: Allow drivers to directly discover INTC hwnode
https://git.kernel.org/riscv/c/0c60a31ce62c
- [v18,3/7] RISC-V: Treat IPIs as normal Linux IRQs
https://git.kernel.org/riscv/c/832f15f42646
- [v18,4/7] RISC-V: Allow marking IPIs as suitable for remote FENCEs
https://git.kernel.org/riscv/c/fb0f3d281b7f
- [v18,5/7] RISC-V: Use IPIs for remote TLB flush when possible
https://git.kernel.org/riscv/c/18d2199d8105
- [v18,6/7] RISC-V: Use IPIs for remote icache flush when possible
https://git.kernel.org/riscv/c/627922843235
- [v18,7/7] irqchip/riscv-intc: Add empty irq_eoi() for chained irq handlers
https://git.kernel.org/riscv/c/f8415f2def18
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-05-08 14:42 UTC|newest]
Thread overview: 27+ 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 ` 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-03-28 3:52 ` Anup Patel
2023-04-08 10:45 ` [irqchip: irq/irqchip-next] " irqchip-bot for Anup Patel
2023-03-28 3:52 ` [PATCH v18 2/7] irqchip/riscv-intc: Allow drivers to directly discover INTC hwnode Anup Patel
2023-03-28 3:52 ` 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-03-28 3:52 ` 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-03-28 3:52 ` 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-03-28 3:52 ` 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-03-28 3:52 ` 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-03-28 3:52 ` 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-03-28 3:56 ` Anup Patel
2023-05-08 14:41 ` patchwork-bot+linux-riscv [this message]
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=168355691627.25692.3962222758677102007.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=Alistair.Francis@wdc.com \
--cc=anup@brainfault.org \
--cc=apatel@ventanamicro.com \
--cc=atishp@atishpatra.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.