diff options
author | Brett Creeley <brett.creeley@intel.com> | 2019-12-12 03:13:02 -0800 |
---|---|---|
committer | Jeff Kirsher <jeffrey.t.kirsher@intel.com> | 2020-01-03 16:08:33 -0800 |
commit | ed4c068d46f69f6f248c6e5a22f69cc84bdb5bb6 (patch) | |
tree | 6a1119214ed183566803e10c3f4ac388343dc25c /drivers/net/ethernet/intel/ice/ice_dcb_lib.c | |
parent | 26a91525cca8e50854706a9e71ce38795ba1fbcb (diff) | |
download | linux-ed4c068d46f69f6f248c6e5a22f69cc84bdb5bb6.tar.gz linux-ed4c068d46f69f6f248c6e5a22f69cc84bdb5bb6.tar.bz2 linux-ed4c068d46f69f6f248c6e5a22f69cc84bdb5bb6.zip |
ice: Enable ip link show on the PF to display VF unicast MAC(s)
Currently when there are SR-IOV VF(s) and the user does "ip link show <pf
interface>" the VF unicast MAC addresses all show 00:00:00:00:00:00
if the unicast MAC was set via VIRTCHNL (i.e. not administratively set
by the host PF).
This is misleading to the host administrator. Fix this by setting the
VF's dflt_lan_addr.addr when the VF's unicast MAC address is
configured via VIRTCHNL. There are a couple cases where we don't allow
the dflt_lan_addr.addr field to be written. First, If the VF's
pf_set_mac field is true and the VF is not trusted, then we don't allow
the dflt_lan_addr.addr to be modified. Second, if the
dflt_lan_addr.addr has already been set (i.e. via VIRTCHNL).
Also a small refactor was done to separate the flow for add and delete
MAC addresses in order to simplify the logic for error conditions
and set/clear the VF's dflt_lan_addr.addr field.
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_dcb_lib.c')
0 files changed, 0 insertions, 0 deletions