summaryrefslogtreecommitdiff
path: root/include/linux/atalk.h
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2024-02-13 10:12:06 +0000
committerThomas Gleixner <tglx@linutronix.de>2024-02-13 11:29:52 +0100
commitaf9acbfc2c4b72c378d0b9a2ee023ed01055d3e2 (patch)
treed650b64733818f79b2c299e6099dd56c9a13b0be /include/linux/atalk.h
parent8b02da04ad978827e5ccd675acf170198f747a7a (diff)
irqchip/gic-v3-its: Fix GICv4.1 VPE affinity update
When updating the affinity of a VPE, the VMOVP command is currently skipped if the two CPUs are part of the same VPE affinity. But this is wrong, as the doorbell corresponding to this VPE is still delivered on the 'old' CPU, which screws up the balancing. Furthermore, offlining that 'old' CPU results in doorbell interrupts generated for this VPE being discarded. The harsh reality is that VMOVP cannot be elided when a set_affinity() request occurs. It needs to be obeyed, and if an optimisation is to be made, it is at the point where the affinity change request is made (such as in KVM). Drop the VMOVP elision altogether, and only use the vpe_table_mask to try and stay within the same ITS affinity group if at all possible. Fixes: dd3f050a216e (irqchip/gic-v4.1: Implement the v4.1 flavour of VMOVP) Reported-by: Kunkun Jiang <jiangkunkun@huawei.com> Signed-off-by: Marc Zyngier <maz@kernel.org> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: stable@vger.kernel.org Link: https://lore.kernel.org/r/20240213101206.2137483-4-maz@kernel.org
Diffstat (limited to 'include/linux/atalk.h')
0 files changed, 0 insertions, 0 deletions