diff options
author | Brett Creeley <brett.creeley@intel.com> | 2020-01-22 07:21:31 -0800 |
---|---|---|
committer | Jeff Kirsher <jeffrey.t.kirsher@intel.com> | 2020-02-15 16:47:20 -0800 |
commit | 2309ae385a42c927be537b25ea89be9a0e64fc4a (patch) | |
tree | c8c1e0683791b5f68c08928c8d1cbea662420ec1 /drivers/rpmsg/qcom_glink_smem.c | |
parent | 39066dc549cf8a688f6e105a4e9f2a8abefbcebe (diff) |
ice: Handle LAN overflow event for VF queues
Currently we are not handling LAN overflow events. There can be cases
where LAN overflow events occur on VF queues, especially with Link Flow
Control (LFC) enabled on the controlling PF. In order to recover from
the LAN overflow event caused by a VF we need to determine if the queue
belongs to a VF and reset that VF accordingly.
The struct ice_aqc_event_lan_overflow returns a copy of the GLDCB_RTCTQ
register, which tells us what the queue index is in the global/device
space. The global queue index needs to first be converted to a PF space
queue index and then it can be used to find if a VF owns it.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'drivers/rpmsg/qcom_glink_smem.c')
0 files changed, 0 insertions, 0 deletions