diff options
author | Jack Morgenstein <jackm@dev.mellanox.co.il> | 2012-05-15 10:35:01 +0000 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2012-05-16 00:56:58 -0400 |
commit | 681372a7a37d4226261e2be2faf3aec5b9e022c2 (patch) | |
tree | a0e407d16a38fd655e5a76c47e63eb0153ca9bfb /drivers/net/can/at91_can.c | |
parent | b9985f410a3b3922a44692566671d7b164b55e71 (diff) | |
download | blackbird-op-linux-681372a7a37d4226261e2be2faf3aec5b9e022c2.tar.gz blackbird-op-linux-681372a7a37d4226261e2be2faf3aec5b9e022c2.zip |
net/mlx4_core: Do not reset module-parameter num_vfs when fail to enable sriov
Consider the following scenario: 2 HCAs, where only one of which can run SRIOV.
If we reset the module parameter, all the VFs of the SRIOV HCA will be
claimed by the PPF host (-- the code relies on num_vfs being non-zero
to avoid this claiming, and num_vfs was reset when pci_enable_sriov failed
for the non-SRIOV HCA).
The solution is not to touch the num_vfs parameter.
Also, eliminate the unneeded check of num_vfs when disabling sriov
(the dev flag bit is sufficient).
Signed-off-by: Jack Morgenstein <jackm@dev.mellanox.co.il>
Signed-off-by: Or Gerlitz <ogerlitz@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/can/at91_can.c')
0 files changed, 0 insertions, 0 deletions