diff options
| author | Stephen Hemminger <[email protected]> | 2020-08-04 09:54:15 -0700 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2020-08-04 16:15:16 -0700 |
| commit | 7c9864bbccc23e1812ac82966555d68c13ea4006 (patch) | |
| tree | 0de13b60ef54f18313812bc3c9e675fbae69d979 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 02afa9c66bb954c6959877c70d9e128dcf0adce7 (diff) | |
hv_netvsc: do not use VF device if link is down
If the accelerated networking SRIOV VF device has lost carrier
use the synthetic network device which is available as backup
path. This is a rare case since if VF link goes down, normally
the VMBus device will also loose external connectivity as well.
But if the communication is between two VM's on the same host
the VMBus device will still work.
Reported-by: "Shah, Ashish N" <[email protected]>
Fixes: 0c195567a8f6 ("netvsc: transparent VF management")
Signed-off-by: Stephen Hemminger <[email protected]>
Reviewed-by: Haiyang Zhang <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions