[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<174957291849.2454024.7268696984666677694.git-patchwork-notify@kernel.org>
Date: Tue, 10 Jun 2025 16:28:38 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Andrew Bresticker <abrestic@...osinc.com>
Cc: linux-riscv@...ts.infradead.org, anup@...infault.org, tglx@...utronix.de,
palmer@...belt.com, alex@...ti.fr, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] irqchip/riscv-imsic: Start local sync timer on correct
CPU
Hello:
This patch was applied to riscv/linux.git (fixes)
by Thomas Gleixner <tglx@...utronix.de>:
On Wed, 14 May 2025 10:13:20 -0700 you wrote:
> When starting the local sync timer to synchronize the state of a remote
> CPU it should be added on the CPU to be synchronized, not the initiating
> CPU. This results in interrupt delivery being delayed until the timer
> eventually runs (due to another mask/unmask/migrate operation) on the
> target CPU.
>
> Fixes: 0f67911e821c ("irqchip/riscv-imsic: Separate next and previous pointers in IMSIC vector")
> Signed-off-by: Andrew Bresticker <abrestic@...osinc.com>
>
> [...]
Here is the summary with links:
- irqchip/riscv-imsic: Start local sync timer on correct CPU
https://git.kernel.org/riscv/c/08fb624802d8
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