diff options
| author | Guilherme G Piccoli <gpiccoli@linux.vnet.ibm.com> | 2016-09-22 10:03:58 -0300 |
|---|---|---|
| committer | Jeff Kirsher <jeffrey.t.kirsher@intel.com> | 2016-10-27 14:10:49 -0700 |
| commit | 4c95aa5d8fc34be18fcab01b1c6251c8c2b61520 (patch) | |
| tree | 5d8381b39bbec0ac0e044e7d31bd90819bb55408 /tools/perf/scripts/python/bin | |
| parent | i40e: Fix configure TCs after initial DCB disable (diff) | |
| download | linux-4c95aa5d8fc34be18fcab01b1c6251c8c2b61520.tar.gz linux-4c95aa5d8fc34be18fcab01b1c6251c8c2b61520.zip | |
i40e: disable MSI-X interrupts if we cannot reserve enough vectors
If we fail on allocating enough MSI-X interrupts, we should disable
them since they were previously enabled in this point of code.
Not disabling them can lead to WARN_ON() being triggered and subsequent
failure in enabling MSI as a fallback; the below message was shown without
this patch while we played with interrupt allocation in i40e driver:
[ 21.461346] sysfs: cannot create duplicate filename '/devices/pci0007:00/0007:00:00.0/0007:01:00.3/msi_irqs'
[ 21.461459] ------------[ cut here ]------------
[ 21.461514] WARNING: CPU: 64 PID: 1155 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x88/0xc0
Also, we noticed that without this patch, if we modprobe the module without
enough MSI-X interrupts (triggering the above warning), unload the module
and re-load it again, we got a crash on the system.
Signed-off-by: Guilherme G Piccoli <gpiccoli@linux.vnet.ibm.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions