[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<175486033674.1221929.9986171280702761593.git-patchwork-notify@kernel.org>
Date: Sun, 10 Aug 2025 21:12:16 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Anup Patel <apatel@...tanamicro.com>
Cc: linux-riscv@...ts.infradead.org, corbet@....net, tglx@...utronix.de,
anup@...infault.org, atish.patra@...ux.dev, palmer@...belt.com,
paul.walmsley@...ive.com, alex@...ti.fr, ajones@...tanamicro.com,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] irqchip/riscv-imsic: Add kernel parameter to disable
IPIs
Hello:
This patch was applied to riscv/linux.git (fixes)
by Thomas Gleixner <tglx@...utronix.de>:
On Wed, 16 Jul 2025 18:07:45 +0530 you wrote:
> When injecting IPIs to a set of harts, the IMSIC IPI support will do
> a separate MMIO write to the SETIPNUM_LE register of each target hart.
> This means on a platform where IMSIC is trap-n-emulated, there will be
> N MMIO traps when injecting IPI to N target harts hence IMSIC IPIs will
> be slow on such platform compared to the SBI IPI extension.
>
> Unfortunately, there is no DT, ACPI, or any other way of discovering
> whether the underlying IMSIC is trap-n-emulated. Using MMIO write to
> the SETIPNUM_LE register for injecting IPI is purely a software choice
> in the IMSIC driver hence add a kernel parameter to allow users disable
> IMSIC IPIs on platforms with trap-n-emulated IMSIC.
>
> [...]
Here is the summary with links:
- [v4] irqchip/riscv-imsic: Add kernel parameter to disable IPIs
https://git.kernel.org/riscv/c/ea92b6046d35
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists