summaryrefslogtreecommitdiffstats
path: root/tools/lib/python
diff options
context:
space:
mode:
authorYong-Xuan Wang <yongxuan.wang@sifive.com>2026-05-08 02:31:21 -0700
committerThomas Gleixner <tglx@kernel.org>2026-05-11 15:23:11 +0200
commitcefafbd561402b0fe6447449364a30315b9b1570 (patch)
treeb2564e6c2e426f6a059949a0fc3ed7fc193fa670 /tools/lib/python
parent5363b67ac8ebcc3e227dbf59fc8061949109841d (diff)
downloadlinux-cefafbd561402b0fe6447449364a30315b9b1570.tar.gz
linux-cefafbd561402b0fe6447449364a30315b9b1570.zip
irqchip/riscv-imsic: Clear interrupt move state during CPU offlining
Affinity changes of IMSIC interrupts have to be careful to not lose an interrupt in the process. Each vector keeps track of an affinity change in progress with two pointers in struct imsic_vector. imsic_vector::move_prev points to the previous CPU target data and imsic_vector::move_next to the designated new CPU target data. imsic_vector::move_prev on the new CPU can only be cleared after the previous CPU has cleared imsic_vector::move_next, which ususally happens in __imsic_remote_sync(). In case of CPU hot-unplug __imsic_remote_sync() is not invoked because the CPU is already marked offline. That means imsic_vector::move_prev becomes stale until the CPU is onlined again. The stale pointer prevents further affinity changes for the affected interrupts. Solve this by clearing the imsic_vector::move_prev pointers in the CPU hotplug offline path. [ tglx: Replace word salad in change log ] Fixes: 0f67911e821c ("irqchip/riscv-imsic: Separate next and previous pointers in IMSIC vector") Signed-off-by: Yong-Xuan Wang <yongxuan.wang@sifive.com> Signed-off-by: Thomas Gleixner <tglx@kernel.org> Cc: stable@vger.kernel.org Link: https://patch.msgid.link/20260508-imsic-v2-1-e9f08dd46cf5@sifive.com
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions