summaryrefslogtreecommitdiff
path: root/lib/mpi/mpi-pow.c
diff options
context:
space:
mode:
authorYonglong Liu <liuyonglong@huawei.com>2025-04-30 12:30:50 +0300
committerJakub Kicinski <kuba@kernel.org>2025-05-01 17:19:48 +0300
commit8e6b9c6ea5a55045eed6526d8ee49e93192d1a58 (patch)
treeb3334cb104e9a0444fe40adf3da599c2d47f58b9 /lib/mpi/mpi-pow.c
parentef2383d078edcbe3055032436b16cdf206f26de2 (diff)
downloadlinux-8e6b9c6ea5a55045eed6526d8ee49e93192d1a58.tar.xz
net: hns3: fix an interrupt residual problem
When a VF is passthrough to a VM, and the VM is killed, the reported interrupt may not been handled, it will remain, and won't be clear by the nic engine even with a flr or tqp reset. When the VM restart, the interrupt of the first vector may be dropped by the second enable_irq in vfio, see the issue below: https://gitlab.com/qemu-project/qemu/-/issues/2884#note_2423361621 We notice that the vfio has always behaved this way, and the interrupt is a residue of the nic engine, so we fix the problem by moving the vector enable process out of the enable_irq loop. Fixes: 08a100689d4b ("net: hns3: re-organize vector handle") Signed-off-by: Yonglong Liu <liuyonglong@huawei.com> Signed-off-by: Jijie Shao <shaojijie@huawei.com> Link: https://patch.msgid.link/20250430093052.2400464-3-shaojijie@huawei.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'lib/mpi/mpi-pow.c')
0 files changed, 0 insertions, 0 deletions