bnx2x: Prevent inner-reload while VFs exist

Browse source

On some feature changes, driver employes an inner-reload flow where it
resets the function and re-configures it with the new required set of
parameters.

Such a flow proves fatal to any VF since those were not intended to be used
while HW is being reset underneath, causing them [at best] to lose all
connectivity.

This changes driver behavior to fail all configuration changes [e.g., mtu
change] requested of the driver in case VFs are active.

Signed-off-by: Yuval Mintz <Yuval.Mintz@qlogic.com>
Signed-off-by: Ariel Elior <Ariel.Elior@qlogic.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

...

This commit is contained in:

Yuval Mintz 2015-04-22 12:47:32 +03:00 • committed by David S. Miller

parent a2c3935aaa

commit 909d9faae2

2 changed files with 51 additions and 9 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

43

drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c

View file

17

drivers/net/ethernet/broadcom/bnx2x/bnx2x_ethtool.c

View file