summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/flamegraph.py
diff options
context:
space:
mode:
authorArun Easi <aeasi@cisco.com>2026-09-03 10:55:47 -0700
committerMartin K. Petersen (Oracle) <mkp@kernel.org>2026-09-09 21:44:18 -0400
commit0cb1fd924126f1f581621a5e804df98a02be9dff (patch)
tree18afa6e0076d0c52402aa5c0a9ac235c44dd8762 /tools/perf/scripts/python/flamegraph.py
parent1274045b0eda1df5a5cdd3e63ed48cf013b3b4ea (diff)
downloadlinux-next-0cb1fd924126f1f581621a5e804df98a02be9dff.tar.gz
linux-next-0cb1fd924126f1f581621a5e804df98a02be9dff.zip
scsi: fnic: Fix missed link-up when critical IRQ targets offline CPU
When CPU Hyper Threading is disabled, sibling CPUs remain present but are reported offline. Managed MSI-X IRQs can still receive affinity masks that include those offline CPUs. If a driver-critical vector is managed, it can be parked on an offline CPU and the driver may miss critical events such as link-up. Keep driver-critical vectors unmanaged so they can be migrated by the IRQ core when their target CPU is offlined. Since HWQ-0 is unmanaged now, in some queue combinations there can be no mappings to it in mq_map. So without the blk-mq fix mentioned below, system may crash during cpu offline/online tests. Fixes: 8a8449ca5e33 ("scsi: fnic: Modify ISRs to support multiqueue (MQ)") Cc: stable@vger.kernel.org Depends-on: commit 10845a105bbc ("blk-mq: skip CPU offline notify on unmapped hctx") Reviewed-by: Sesidhar Baddela <sebaddel@cisco.com> Reviewed-by: Arulprabhu Ponnusamy <arulponn@cisco.com> Reviewed-by: Gian Carlo Boffa <gcboffa@cisco.com> Reviewed-by: Karan Tilak Kumar <kartilak@cisco.com> Signed-off-by: Arun Easi <aeasi@cisco.com> Reviewed-by: Laurence Oberman <loberman@redhat.com> Link: https://patch.msgid.link/20260903175547.57971-1-aeasi@cisco.com Signed-off-by: Martin K. Petersen (Oracle) <mkp@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions