summaryrefslogtreecommitdiffstats
path: root/drivers/dma-buf
diff options
context:
space:
mode:
authorMichal Swiatkowski <michal.swiatkowski@linux.intel.com>2021-10-13 08:27:07 +0200
committerTony Nguyen <anthony.l.nguyen@intel.com>2021-10-28 11:00:20 -0700
commite492c2e12d7bb2cf3f10abd8038431e7de565058 (patch)
tree768cf3e31ae996b84b2ca609c63179e4073a2014 /drivers/dma-buf
parentf0a35040adbe72f6b2e9ddc9fefdbcdbe0b92c55 (diff)
downloadlinux-stable-e492c2e12d7bb2cf3f10abd8038431e7de565058.tar.gz
linux-stable-e492c2e12d7bb2cf3f10abd8038431e7de565058.tar.bz2
linux-stable-e492c2e12d7bb2cf3f10abd8038431e7de565058.zip
ice: send correct vc status in switchdev
Part of virtchannel messages are treated in different way in switchdev mode to block configuring VFs from iavf driver side. This blocking was done by doing nothing and returning success, event without sending response. Not sending response for opcodes that aren't supported in switchdev mode leads to block iavf driver message handling. This happens for example when vlan is configured at VF config time (VLAN module is already loaded). To get rid of it ice driver should answer for each VF message. In switchdev mode: - for adding/deleting VLAN driver should answer success without doing anything to allow creating vlan device on VFs - for enabling/disabling VLAN stripping and promiscuous mode driver should answer not supported, this feature in switchdev can be only set from host side Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com> Tested-by: Sandeep Penigalapati <sandeep.penigalapati@intel.com> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
Diffstat (limited to 'drivers/dma-buf')
0 files changed, 0 insertions, 0 deletions