diff options
| author | Brett Creeley <brett.creeley@intel.com> | 2019-11-06 02:05:34 -0800 |
|---|---|---|
| committer | Jeff Kirsher <jeffrey.t.kirsher@intel.com> | 2019-11-08 12:02:56 -0800 |
| commit | b791cdd5c78c74a165ee8da69d6c8ae683d17c38 (patch) | |
| tree | 54aa347bf468df3c51e332ba836d3aa6e6d45342 /drivers/net/ethernet/intel/ice/ice_controlq.c | |
| parent | ec4f5a436bdf0e5453ad15c4f34a59b9b675ff48 (diff) | |
| download | kernel_replicant_linux-b791cdd5c78c74a165ee8da69d6c8ae683d17c38.tar.gz kernel_replicant_linux-b791cdd5c78c74a165ee8da69d6c8ae683d17c38.tar.bz2 kernel_replicant_linux-b791cdd5c78c74a165ee8da69d6c8ae683d17c38.zip | |
ice: Change max MSI-x vector_id check in cfg_irq_map
Currently we check to make sure the vector_id passed down from iavf
is less than or equal to pf->hw.func_caps.common_caps.num_msix_vectors.
This is incorrect because the vector_id is always 0-based and never
greater than or equal to the ICE_MAX_INTR_PER_VF. Fix this by checking
to make sure the vector_id is less than the max allowed interrupts per
VF (ICE_MAX_INTR_PER_VF).
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'drivers/net/ethernet/intel/ice/ice_controlq.c')
0 files changed, 0 insertions, 0 deletions