diff options
| author | Jason Andryuk <jason.andryuk@amd.com> | 2025-10-17 09:41:17 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-10-19 16:23:23 +0200 |
| commit | b8291d6d98545d954f3d7fa46f5655e2b8a23973 (patch) | |
| tree | 4cc79fb74b8198ec48e7305b18e4906c55a54078 /crypto/xor.c | |
| parent | db62b1e7b1d3f8e97b59f9f8e07829356d0ff3e4 (diff) | |
| download | linux-b8291d6d98545d954f3d7fa46f5655e2b8a23973.tar.gz linux-b8291d6d98545d954f3d7fa46f5655e2b8a23973.tar.bz2 linux-b8291d6d98545d954f3d7fa46f5655e2b8a23973.zip | |
xen/events: Update virq_to_irq on migration
[ Upstream commit 3fcc8e146935415d69ffabb5df40ecf50e106131 ]
VIRQs come in 3 flavors, per-VPU, per-domain, and global, and the VIRQs
are tracked in per-cpu virq_to_irq arrays.
Per-domain and global VIRQs must be bound on CPU 0, and
bind_virq_to_irq() sets the per_cpu virq_to_irq at registration time
Later, the interrupt can migrate, and info->cpu is updated. When
calling __unbind_from_irq(), the per-cpu virq_to_irq is cleared for a
different cpu. If bind_virq_to_irq() is called again with CPU 0, the
stale irq is returned. There won't be any irq_info for the irq, so
things break.
Make xen_rebind_evtchn_to_cpu() update the per_cpu virq_to_irq mappings
to keep them update to date with the current cpu. This ensures the
correct virq_to_irq is cleared in __unbind_from_irq().
Fixes: e46cdb66c8fc ("xen: event channels")
Cc: stable@vger.kernel.org
Signed-off-by: Jason Andryuk <jason.andryuk@amd.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Signed-off-by: Juergen Gross <jgross@suse.com>
Message-ID: <20250828003604.8949-4-jason.andryuk@amd.com>
[ Adjust context ]
Signed-off-by: Sasha Levin <sashal@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'crypto/xor.c')
0 files changed, 0 insertions, 0 deletions
