2018-03-20 07:58:05 -07:00
|
|
|
// SPDX-License-Identifier: GPL-2.0
|
|
|
|
/* Copyright (c) 2018, Intel Corporation. */
|
|
|
|
|
|
|
|
/* Intel(R) Ethernet Connection E800 Series Linux Driver */
|
|
|
|
|
|
|
|
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
|
|
|
|
|
|
|
|
#include "ice.h"
|
2018-09-19 17:23:04 -07:00
|
|
|
#include "ice_lib.h"
|
2019-02-28 15:24:22 -08:00
|
|
|
#include "ice_dcb_lib.h"
|
2018-03-20 07:58:05 -07:00
|
|
|
|
2019-02-28 15:24:32 -08:00
|
|
|
#define DRV_VERSION "0.7.4-k"
|
2018-03-20 07:58:05 -07:00
|
|
|
#define DRV_SUMMARY "Intel(R) Ethernet Connection E800 Series Linux Driver"
|
2018-03-20 07:58:16 -07:00
|
|
|
const char ice_drv_ver[] = DRV_VERSION;
|
2018-03-20 07:58:05 -07:00
|
|
|
static const char ice_driver_string[] = DRV_SUMMARY;
|
|
|
|
static const char ice_copyright[] = "Copyright (c) 2018, Intel Corporation.";
|
|
|
|
|
|
|
|
MODULE_AUTHOR("Intel Corporation, <linux.nics@intel.com>");
|
|
|
|
MODULE_DESCRIPTION(DRV_SUMMARY);
|
2018-09-14 17:37:57 -07:00
|
|
|
MODULE_LICENSE("GPL v2");
|
2018-03-20 07:58:05 -07:00
|
|
|
MODULE_VERSION(DRV_VERSION);
|
|
|
|
|
|
|
|
static int debug = -1;
|
|
|
|
module_param(debug, int, 0644);
|
2018-03-20 07:58:06 -07:00
|
|
|
#ifndef CONFIG_DYNAMIC_DEBUG
|
|
|
|
MODULE_PARM_DESC(debug, "netif level (0=none,...,16=all), hw debug_mask (0x8XXXXXXX)");
|
|
|
|
#else
|
|
|
|
MODULE_PARM_DESC(debug, "netif level (0=none,...,16=all)");
|
|
|
|
#endif /* !CONFIG_DYNAMIC_DEBUG */
|
2018-03-20 07:58:05 -07:00
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
static struct workqueue_struct *ice_wq;
|
2018-03-20 07:58:13 -07:00
|
|
|
static const struct net_device_ops ice_netdev_ops;
|
2018-03-20 07:58:10 -07:00
|
|
|
|
2018-03-20 07:58:18 -07:00
|
|
|
static void ice_rebuild(struct ice_pf *pf);
|
2018-09-19 17:23:07 -07:00
|
|
|
|
2018-08-09 06:29:50 -07:00
|
|
|
static void ice_vsi_release_all(struct ice_pf *pf);
|
2018-03-20 07:58:16 -07:00
|
|
|
static void ice_update_vsi_stats(struct ice_vsi *vsi);
|
|
|
|
static void ice_update_pf_stats(struct ice_pf *pf);
|
2018-03-20 07:58:11 -07:00
|
|
|
|
2018-08-09 06:29:53 -07:00
|
|
|
/**
|
|
|
|
* ice_get_tx_pending - returns number of Tx descriptors not processed
|
|
|
|
* @ring: the ring of descriptors
|
|
|
|
*/
|
|
|
|
static u32 ice_get_tx_pending(struct ice_ring *ring)
|
|
|
|
{
|
|
|
|
u32 head, tail;
|
|
|
|
|
|
|
|
head = ring->next_to_clean;
|
|
|
|
tail = readl(ring->tail);
|
|
|
|
|
|
|
|
if (head != tail)
|
|
|
|
return (head < tail) ?
|
|
|
|
tail - head : (tail + ring->count - head);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_check_for_hang_subtask - check for and recover hung queues
|
|
|
|
* @pf: pointer to PF struct
|
|
|
|
*/
|
|
|
|
static void ice_check_for_hang_subtask(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
struct ice_vsi *vsi = NULL;
|
2019-04-16 10:30:51 -07:00
|
|
|
struct ice_hw *hw;
|
2018-08-09 06:29:53 -07:00
|
|
|
unsigned int i;
|
|
|
|
int packets;
|
2019-04-16 10:30:51 -07:00
|
|
|
u32 v;
|
2018-08-09 06:29:53 -07:00
|
|
|
|
|
|
|
ice_for_each_vsi(pf, v)
|
|
|
|
if (pf->vsi[v] && pf->vsi[v]->type == ICE_VSI_PF) {
|
|
|
|
vsi = pf->vsi[v];
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!vsi || test_bit(__ICE_DOWN, vsi->state))
|
|
|
|
return;
|
|
|
|
|
|
|
|
if (!(vsi->netdev && netif_carrier_ok(vsi->netdev)))
|
|
|
|
return;
|
|
|
|
|
2019-04-16 10:30:51 -07:00
|
|
|
hw = &vsi->back->hw;
|
|
|
|
|
2018-08-09 06:29:53 -07:00
|
|
|
for (i = 0; i < vsi->num_txq; i++) {
|
|
|
|
struct ice_ring *tx_ring = vsi->tx_rings[i];
|
|
|
|
|
|
|
|
if (tx_ring && tx_ring->desc) {
|
|
|
|
/* If packet counter has not changed the queue is
|
|
|
|
* likely stalled, so force an interrupt for this
|
|
|
|
* queue.
|
|
|
|
*
|
|
|
|
* prev_pkt would be negative if there was no
|
|
|
|
* pending work.
|
|
|
|
*/
|
|
|
|
packets = tx_ring->stats.pkts & INT_MAX;
|
|
|
|
if (tx_ring->tx_stats.prev_pkt == packets) {
|
|
|
|
/* Trigger sw interrupt to revive the queue */
|
2019-04-16 10:30:51 -07:00
|
|
|
ice_trigger_sw_intr(hw, tx_ring->q_vector);
|
2018-08-09 06:29:53 -07:00
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Memory barrier between read of packet count and call
|
|
|
|
* to ice_get_tx_pending()
|
|
|
|
*/
|
|
|
|
smp_rmb();
|
|
|
|
tx_ring->tx_stats.prev_pkt =
|
|
|
|
ice_get_tx_pending(tx_ring) ? packets : -1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:19 -07:00
|
|
|
/**
|
2019-02-19 15:04:13 -08:00
|
|
|
* ice_add_mac_to_sync_list - creates list of MAC addresses to be synced
|
2018-03-20 07:58:19 -07:00
|
|
|
* @netdev: the net device on which the sync is happening
|
2019-02-19 15:04:13 -08:00
|
|
|
* @addr: MAC address to sync
|
2018-03-20 07:58:19 -07:00
|
|
|
*
|
|
|
|
* This is a callback function which is called by the in kernel device sync
|
|
|
|
* functions (like __dev_uc_sync, __dev_mc_sync, etc). This function only
|
|
|
|
* populates the tmp_sync_list, which is later used by ice_add_mac to add the
|
2019-02-19 15:04:13 -08:00
|
|
|
* MAC filters from the hardware.
|
2018-03-20 07:58:19 -07:00
|
|
|
*/
|
|
|
|
static int ice_add_mac_to_sync_list(struct net_device *netdev, const u8 *addr)
|
|
|
|
{
|
|
|
|
struct ice_netdev_priv *np = netdev_priv(netdev);
|
|
|
|
struct ice_vsi *vsi = np->vsi;
|
|
|
|
|
|
|
|
if (ice_add_mac_to_list(vsi, &vsi->tmp_sync_list, addr))
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2019-02-19 15:04:13 -08:00
|
|
|
* ice_add_mac_to_unsync_list - creates list of MAC addresses to be unsynced
|
2018-03-20 07:58:19 -07:00
|
|
|
* @netdev: the net device on which the unsync is happening
|
2019-02-19 15:04:13 -08:00
|
|
|
* @addr: MAC address to unsync
|
2018-03-20 07:58:19 -07:00
|
|
|
*
|
|
|
|
* This is a callback function which is called by the in kernel device unsync
|
|
|
|
* functions (like __dev_uc_unsync, __dev_mc_unsync, etc). This function only
|
|
|
|
* populates the tmp_unsync_list, which is later used by ice_remove_mac to
|
2019-02-19 15:04:13 -08:00
|
|
|
* delete the MAC filters from the hardware.
|
2018-03-20 07:58:19 -07:00
|
|
|
*/
|
|
|
|
static int ice_add_mac_to_unsync_list(struct net_device *netdev, const u8 *addr)
|
|
|
|
{
|
|
|
|
struct ice_netdev_priv *np = netdev_priv(netdev);
|
|
|
|
struct ice_vsi *vsi = np->vsi;
|
|
|
|
|
|
|
|
if (ice_add_mac_to_list(vsi, &vsi->tmp_unsync_list, addr))
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_vsi_fltr_changed - check if filter state changed
|
|
|
|
* @vsi: VSI to be checked
|
|
|
|
*
|
|
|
|
* returns true if filter state has changed, false otherwise.
|
|
|
|
*/
|
|
|
|
static bool ice_vsi_fltr_changed(struct ice_vsi *vsi)
|
|
|
|
{
|
|
|
|
return test_bit(ICE_VSI_FLAG_UMAC_FLTR_CHANGED, vsi->flags) ||
|
|
|
|
test_bit(ICE_VSI_FLAG_MMAC_FLTR_CHANGED, vsi->flags) ||
|
|
|
|
test_bit(ICE_VSI_FLAG_VLAN_FLTR_CHANGED, vsi->flags);
|
|
|
|
}
|
|
|
|
|
2019-02-26 16:35:14 -08:00
|
|
|
/**
|
|
|
|
* ice_cfg_promisc - Enable or disable promiscuous mode for a given PF
|
|
|
|
* @vsi: the VSI being configured
|
|
|
|
* @promisc_m: mask of promiscuous config bits
|
|
|
|
* @set_promisc: enable or disable promisc flag request
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
static int ice_cfg_promisc(struct ice_vsi *vsi, u8 promisc_m, bool set_promisc)
|
|
|
|
{
|
|
|
|
struct ice_hw *hw = &vsi->back->hw;
|
|
|
|
enum ice_status status = 0;
|
|
|
|
|
|
|
|
if (vsi->type != ICE_VSI_PF)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (vsi->vlan_ena) {
|
|
|
|
status = ice_set_vlan_vsi_promisc(hw, vsi->idx, promisc_m,
|
|
|
|
set_promisc);
|
|
|
|
} else {
|
|
|
|
if (set_promisc)
|
|
|
|
status = ice_set_vsi_promisc(hw, vsi->idx, promisc_m,
|
|
|
|
0);
|
|
|
|
else
|
|
|
|
status = ice_clear_vsi_promisc(hw, vsi->idx, promisc_m,
|
|
|
|
0);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (status)
|
|
|
|
return -EIO;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:19 -07:00
|
|
|
/**
|
|
|
|
* ice_vsi_sync_fltr - Update the VSI filter list to the HW
|
|
|
|
* @vsi: ptr to the VSI
|
|
|
|
*
|
|
|
|
* Push any outstanding VSI filter changes through the AdminQ.
|
|
|
|
*/
|
|
|
|
static int ice_vsi_sync_fltr(struct ice_vsi *vsi)
|
|
|
|
{
|
|
|
|
struct device *dev = &vsi->back->pdev->dev;
|
|
|
|
struct net_device *netdev = vsi->netdev;
|
|
|
|
bool promisc_forced_on = false;
|
|
|
|
struct ice_pf *pf = vsi->back;
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
enum ice_status status = 0;
|
|
|
|
u32 changed_flags = 0;
|
2019-02-26 16:35:14 -08:00
|
|
|
u8 promisc_m;
|
2018-03-20 07:58:19 -07:00
|
|
|
int err = 0;
|
|
|
|
|
|
|
|
if (!vsi->netdev)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
while (test_and_set_bit(__ICE_CFG_BUSY, vsi->state))
|
|
|
|
usleep_range(1000, 2000);
|
|
|
|
|
|
|
|
changed_flags = vsi->current_netdev_flags ^ vsi->netdev->flags;
|
|
|
|
vsi->current_netdev_flags = vsi->netdev->flags;
|
|
|
|
|
|
|
|
INIT_LIST_HEAD(&vsi->tmp_sync_list);
|
|
|
|
INIT_LIST_HEAD(&vsi->tmp_unsync_list);
|
|
|
|
|
|
|
|
if (ice_vsi_fltr_changed(vsi)) {
|
|
|
|
clear_bit(ICE_VSI_FLAG_UMAC_FLTR_CHANGED, vsi->flags);
|
|
|
|
clear_bit(ICE_VSI_FLAG_MMAC_FLTR_CHANGED, vsi->flags);
|
|
|
|
clear_bit(ICE_VSI_FLAG_VLAN_FLTR_CHANGED, vsi->flags);
|
|
|
|
|
|
|
|
/* grab the netdev's addr_list_lock */
|
|
|
|
netif_addr_lock_bh(netdev);
|
|
|
|
__dev_uc_sync(netdev, ice_add_mac_to_sync_list,
|
|
|
|
ice_add_mac_to_unsync_list);
|
|
|
|
__dev_mc_sync(netdev, ice_add_mac_to_sync_list,
|
|
|
|
ice_add_mac_to_unsync_list);
|
|
|
|
/* our temp lists are populated. release lock */
|
|
|
|
netif_addr_unlock_bh(netdev);
|
|
|
|
}
|
|
|
|
|
2019-02-19 15:04:13 -08:00
|
|
|
/* Remove MAC addresses in the unsync list */
|
2018-03-20 07:58:19 -07:00
|
|
|
status = ice_remove_mac(hw, &vsi->tmp_unsync_list);
|
|
|
|
ice_free_fltr_list(dev, &vsi->tmp_unsync_list);
|
|
|
|
if (status) {
|
|
|
|
netdev_err(netdev, "Failed to delete MAC filters\n");
|
|
|
|
/* if we failed because of alloc failures, just bail */
|
|
|
|
if (status == ICE_ERR_NO_MEMORY) {
|
|
|
|
err = -ENOMEM;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2019-02-19 15:04:13 -08:00
|
|
|
/* Add MAC addresses in the sync list */
|
2018-03-20 07:58:19 -07:00
|
|
|
status = ice_add_mac(hw, &vsi->tmp_sync_list);
|
|
|
|
ice_free_fltr_list(dev, &vsi->tmp_sync_list);
|
2019-02-19 15:04:04 -08:00
|
|
|
/* If filter is added successfully or already exists, do not go into
|
|
|
|
* 'if' condition and report it as error. Instead continue processing
|
|
|
|
* rest of the function.
|
|
|
|
*/
|
|
|
|
if (status && status != ICE_ERR_ALREADY_EXISTS) {
|
2018-03-20 07:58:19 -07:00
|
|
|
netdev_err(netdev, "Failed to add MAC filters\n");
|
2019-02-19 15:04:13 -08:00
|
|
|
/* If there is no more space for new umac filters, VSI
|
2018-03-20 07:58:19 -07:00
|
|
|
* should go into promiscuous mode. There should be some
|
|
|
|
* space reserved for promiscuous filters.
|
|
|
|
*/
|
|
|
|
if (hw->adminq.sq_last_status == ICE_AQ_RC_ENOSPC &&
|
|
|
|
!test_and_set_bit(__ICE_FLTR_OVERFLOW_PROMISC,
|
|
|
|
vsi->state)) {
|
|
|
|
promisc_forced_on = true;
|
|
|
|
netdev_warn(netdev,
|
|
|
|
"Reached MAC filter limit, forcing promisc mode on VSI %d\n",
|
|
|
|
vsi->vsi_num);
|
|
|
|
} else {
|
|
|
|
err = -EIO;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
/* check for changes in promiscuous modes */
|
2019-02-26 16:35:14 -08:00
|
|
|
if (changed_flags & IFF_ALLMULTI) {
|
|
|
|
if (vsi->current_netdev_flags & IFF_ALLMULTI) {
|
|
|
|
if (vsi->vlan_ena)
|
|
|
|
promisc_m = ICE_MCAST_VLAN_PROMISC_BITS;
|
|
|
|
else
|
|
|
|
promisc_m = ICE_MCAST_PROMISC_BITS;
|
|
|
|
|
|
|
|
err = ice_cfg_promisc(vsi, promisc_m, true);
|
|
|
|
if (err) {
|
|
|
|
netdev_err(netdev, "Error setting Multicast promiscuous mode on VSI %i\n",
|
|
|
|
vsi->vsi_num);
|
|
|
|
vsi->current_netdev_flags &= ~IFF_ALLMULTI;
|
|
|
|
goto out_promisc;
|
|
|
|
}
|
|
|
|
} else if (!(vsi->current_netdev_flags & IFF_ALLMULTI)) {
|
|
|
|
if (vsi->vlan_ena)
|
|
|
|
promisc_m = ICE_MCAST_VLAN_PROMISC_BITS;
|
|
|
|
else
|
|
|
|
promisc_m = ICE_MCAST_PROMISC_BITS;
|
|
|
|
|
|
|
|
err = ice_cfg_promisc(vsi, promisc_m, false);
|
|
|
|
if (err) {
|
|
|
|
netdev_err(netdev, "Error clearing Multicast promiscuous mode on VSI %i\n",
|
|
|
|
vsi->vsi_num);
|
|
|
|
vsi->current_netdev_flags |= IFF_ALLMULTI;
|
|
|
|
goto out_promisc;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2018-03-20 07:58:19 -07:00
|
|
|
|
|
|
|
if (((changed_flags & IFF_PROMISC) || promisc_forced_on) ||
|
|
|
|
test_bit(ICE_VSI_FLAG_PROMISC_CHANGED, vsi->flags)) {
|
|
|
|
clear_bit(ICE_VSI_FLAG_PROMISC_CHANGED, vsi->flags);
|
|
|
|
if (vsi->current_netdev_flags & IFF_PROMISC) {
|
2019-02-19 15:04:13 -08:00
|
|
|
/* Apply Rx filter rule to get traffic from wire */
|
2018-09-19 17:23:13 -07:00
|
|
|
status = ice_cfg_dflt_vsi(hw, vsi->idx, true,
|
2018-03-20 07:58:19 -07:00
|
|
|
ICE_FLTR_RX);
|
|
|
|
if (status) {
|
2019-04-16 10:21:27 -07:00
|
|
|
netdev_err(netdev, "Error setting default VSI %i Rx rule\n",
|
2018-03-20 07:58:19 -07:00
|
|
|
vsi->vsi_num);
|
|
|
|
vsi->current_netdev_flags &= ~IFF_PROMISC;
|
|
|
|
err = -EIO;
|
|
|
|
goto out_promisc;
|
|
|
|
}
|
|
|
|
} else {
|
2019-02-19 15:04:13 -08:00
|
|
|
/* Clear Rx filter to remove traffic from wire */
|
2018-09-19 17:23:13 -07:00
|
|
|
status = ice_cfg_dflt_vsi(hw, vsi->idx, false,
|
2018-03-20 07:58:19 -07:00
|
|
|
ICE_FLTR_RX);
|
|
|
|
if (status) {
|
2019-04-16 10:21:27 -07:00
|
|
|
netdev_err(netdev, "Error clearing default VSI %i Rx rule\n",
|
2018-03-20 07:58:19 -07:00
|
|
|
vsi->vsi_num);
|
|
|
|
vsi->current_netdev_flags |= IFF_PROMISC;
|
|
|
|
err = -EIO;
|
|
|
|
goto out_promisc;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
goto exit;
|
|
|
|
|
|
|
|
out_promisc:
|
|
|
|
set_bit(ICE_VSI_FLAG_PROMISC_CHANGED, vsi->flags);
|
|
|
|
goto exit;
|
|
|
|
out:
|
|
|
|
/* if something went wrong then set the changed flag so we try again */
|
|
|
|
set_bit(ICE_VSI_FLAG_UMAC_FLTR_CHANGED, vsi->flags);
|
|
|
|
set_bit(ICE_VSI_FLAG_MMAC_FLTR_CHANGED, vsi->flags);
|
|
|
|
exit:
|
|
|
|
clear_bit(__ICE_CFG_BUSY, vsi->state);
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_sync_fltr_subtask - Sync the VSI filter list with HW
|
|
|
|
* @pf: board private structure
|
|
|
|
*/
|
|
|
|
static void ice_sync_fltr_subtask(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
int v;
|
|
|
|
|
|
|
|
if (!pf || !(test_bit(ICE_FLAG_FLTR_SYNC, pf->flags)))
|
|
|
|
return;
|
|
|
|
|
|
|
|
clear_bit(ICE_FLAG_FLTR_SYNC, pf->flags);
|
|
|
|
|
2019-02-08 12:50:54 -08:00
|
|
|
ice_for_each_vsi(pf, v)
|
2018-03-20 07:58:19 -07:00
|
|
|
if (pf->vsi[v] && ice_vsi_fltr_changed(pf->vsi[v]) &&
|
|
|
|
ice_vsi_sync_fltr(pf->vsi[v])) {
|
|
|
|
/* come back and try again later */
|
|
|
|
set_bit(ICE_FLAG_FLTR_SYNC, pf->flags);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2019-02-28 15:24:24 -08:00
|
|
|
/**
|
|
|
|
* ice_dis_vsi - pause a VSI
|
|
|
|
* @vsi: the VSI being paused
|
|
|
|
* @locked: is the rtnl_lock already held
|
|
|
|
*/
|
|
|
|
static void ice_dis_vsi(struct ice_vsi *vsi, bool locked)
|
|
|
|
{
|
|
|
|
if (test_bit(__ICE_DOWN, vsi->state))
|
|
|
|
return;
|
|
|
|
|
|
|
|
set_bit(__ICE_NEEDS_RESTART, vsi->state);
|
|
|
|
|
|
|
|
if (vsi->type == ICE_VSI_PF && vsi->netdev) {
|
|
|
|
if (netif_running(vsi->netdev)) {
|
|
|
|
if (!locked) {
|
|
|
|
rtnl_lock();
|
|
|
|
vsi->netdev->netdev_ops->ndo_stop(vsi->netdev);
|
|
|
|
rtnl_unlock();
|
|
|
|
} else {
|
|
|
|
vsi->netdev->netdev_ops->ndo_stop(vsi->netdev);
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
ice_vsi_close(vsi);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_pf_dis_all_vsi - Pause all VSIs on a PF
|
|
|
|
* @pf: the PF
|
|
|
|
* @locked: is the rtnl_lock already held
|
|
|
|
*/
|
|
|
|
#ifdef CONFIG_DCB
|
|
|
|
void ice_pf_dis_all_vsi(struct ice_pf *pf, bool locked)
|
|
|
|
#else
|
|
|
|
static void ice_pf_dis_all_vsi(struct ice_pf *pf, bool locked)
|
|
|
|
#endif /* CONFIG_DCB */
|
|
|
|
{
|
|
|
|
int v;
|
|
|
|
|
|
|
|
ice_for_each_vsi(pf, v)
|
|
|
|
if (pf->vsi[v])
|
|
|
|
ice_dis_vsi(pf->vsi[v], locked);
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:18 -07:00
|
|
|
/**
|
|
|
|
* ice_prepare_for_reset - prep for the core to reset
|
|
|
|
* @pf: board private structure
|
|
|
|
*
|
|
|
|
* Inform or close all dependent features in prep for reset.
|
|
|
|
*/
|
|
|
|
static void
|
|
|
|
ice_prepare_for_reset(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
|
2019-02-13 10:51:14 -08:00
|
|
|
/* already prepared for reset */
|
|
|
|
if (test_bit(__ICE_PREPARED_FOR_RESET, pf->state))
|
|
|
|
return;
|
|
|
|
|
2018-09-19 17:42:57 -07:00
|
|
|
/* Notify VFs of impending reset */
|
|
|
|
if (ice_check_sq_alive(hw, &hw->mailboxq))
|
|
|
|
ice_vc_notify_reset(pf);
|
|
|
|
|
2018-03-20 07:58:18 -07:00
|
|
|
/* disable the VSIs and their queues that are not already DOWN */
|
2019-02-28 15:24:24 -08:00
|
|
|
ice_pf_dis_all_vsi(pf, false);
|
2018-03-20 07:58:18 -07:00
|
|
|
|
2018-10-26 11:44:35 -07:00
|
|
|
if (hw->port_info)
|
|
|
|
ice_sched_clear_port(hw->port_info);
|
|
|
|
|
2018-03-20 07:58:18 -07:00
|
|
|
ice_shutdown_all_ctrlq(hw);
|
2018-08-09 06:29:50 -07:00
|
|
|
|
|
|
|
set_bit(__ICE_PREPARED_FOR_RESET, pf->state);
|
2018-03-20 07:58:18 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_do_reset - Initiate one of many types of resets
|
|
|
|
* @pf: board private structure
|
|
|
|
* @reset_type: reset type requested
|
|
|
|
* before this function was called.
|
|
|
|
*/
|
|
|
|
static void ice_do_reset(struct ice_pf *pf, enum ice_reset_req reset_type)
|
|
|
|
{
|
|
|
|
struct device *dev = &pf->pdev->dev;
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
|
|
|
|
dev_dbg(dev, "reset_type 0x%x requested\n", reset_type);
|
|
|
|
WARN_ON(in_interrupt());
|
|
|
|
|
2018-08-09 06:29:50 -07:00
|
|
|
ice_prepare_for_reset(pf);
|
2018-03-20 07:58:18 -07:00
|
|
|
|
|
|
|
/* trigger the reset */
|
|
|
|
if (ice_reset(hw, reset_type)) {
|
|
|
|
dev_err(dev, "reset %d failed\n", reset_type);
|
|
|
|
set_bit(__ICE_RESET_FAILED, pf->state);
|
2018-09-19 17:23:11 -07:00
|
|
|
clear_bit(__ICE_RESET_OICR_RECV, pf->state);
|
2018-08-09 06:29:50 -07:00
|
|
|
clear_bit(__ICE_PREPARED_FOR_RESET, pf->state);
|
2018-09-19 17:23:11 -07:00
|
|
|
clear_bit(__ICE_PFR_REQ, pf->state);
|
|
|
|
clear_bit(__ICE_CORER_REQ, pf->state);
|
|
|
|
clear_bit(__ICE_GLOBR_REQ, pf->state);
|
2018-03-20 07:58:18 -07:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2018-08-09 06:29:50 -07:00
|
|
|
/* PFR is a bit of a special case because it doesn't result in an OICR
|
|
|
|
* interrupt. So for PFR, rebuild after the reset and clear the reset-
|
|
|
|
* associated state bits.
|
|
|
|
*/
|
2018-03-20 07:58:18 -07:00
|
|
|
if (reset_type == ICE_RESET_PFR) {
|
|
|
|
pf->pfr_count++;
|
|
|
|
ice_rebuild(pf);
|
2018-08-09 06:29:50 -07:00
|
|
|
clear_bit(__ICE_PREPARED_FOR_RESET, pf->state);
|
2018-09-19 17:23:11 -07:00
|
|
|
clear_bit(__ICE_PFR_REQ, pf->state);
|
2019-02-08 12:50:56 -08:00
|
|
|
ice_reset_all_vfs(pf, true);
|
2018-03-20 07:58:18 -07:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_reset_subtask - Set up for resetting the device and driver
|
|
|
|
* @pf: board private structure
|
|
|
|
*/
|
|
|
|
static void ice_reset_subtask(struct ice_pf *pf)
|
|
|
|
{
|
2018-08-09 06:29:50 -07:00
|
|
|
enum ice_reset_req reset_type = ICE_RESET_INVAL;
|
2018-03-20 07:58:18 -07:00
|
|
|
|
|
|
|
/* When a CORER/GLOBR/EMPR is about to happen, the hardware triggers an
|
2018-08-09 06:29:50 -07:00
|
|
|
* OICR interrupt. The OICR handler (ice_misc_intr) determines what type
|
|
|
|
* of reset is pending and sets bits in pf->state indicating the reset
|
2018-10-26 11:44:46 -07:00
|
|
|
* type and __ICE_RESET_OICR_RECV. So, if the latter bit is set
|
2018-08-09 06:29:50 -07:00
|
|
|
* prepare for pending reset if not already (for PF software-initiated
|
|
|
|
* global resets the software should already be prepared for it as
|
|
|
|
* indicated by __ICE_PREPARED_FOR_RESET; for global resets initiated
|
|
|
|
* by firmware or software on other PFs, that bit is not set so prepare
|
|
|
|
* for the reset now), poll for reset done, rebuild and return.
|
2018-03-20 07:58:18 -07:00
|
|
|
*/
|
2018-09-19 17:23:11 -07:00
|
|
|
if (test_bit(__ICE_RESET_OICR_RECV, pf->state)) {
|
2019-02-13 10:51:08 -08:00
|
|
|
/* Perform the largest reset requested */
|
|
|
|
if (test_and_clear_bit(__ICE_CORER_RECV, pf->state))
|
|
|
|
reset_type = ICE_RESET_CORER;
|
|
|
|
if (test_and_clear_bit(__ICE_GLOBR_RECV, pf->state))
|
|
|
|
reset_type = ICE_RESET_GLOBR;
|
|
|
|
/* return if no valid reset type requested */
|
|
|
|
if (reset_type == ICE_RESET_INVAL)
|
|
|
|
return;
|
2019-02-13 10:51:14 -08:00
|
|
|
ice_prepare_for_reset(pf);
|
2018-03-20 07:58:18 -07:00
|
|
|
|
|
|
|
/* make sure we are ready to rebuild */
|
2018-08-09 06:29:47 -07:00
|
|
|
if (ice_check_reset(&pf->hw)) {
|
2018-03-20 07:58:18 -07:00
|
|
|
set_bit(__ICE_RESET_FAILED, pf->state);
|
2018-08-09 06:29:47 -07:00
|
|
|
} else {
|
|
|
|
/* done with reset. start rebuild */
|
|
|
|
pf->hw.reset_ongoing = false;
|
2018-03-20 07:58:18 -07:00
|
|
|
ice_rebuild(pf);
|
2018-08-09 06:29:50 -07:00
|
|
|
/* clear bit to resume normal operations, but
|
2019-02-19 15:04:12 -08:00
|
|
|
* ICE_NEEDS_RESTART bit is set in case rebuild failed
|
2018-08-09 06:29:50 -07:00
|
|
|
*/
|
2018-09-19 17:23:11 -07:00
|
|
|
clear_bit(__ICE_RESET_OICR_RECV, pf->state);
|
2018-08-09 06:29:50 -07:00
|
|
|
clear_bit(__ICE_PREPARED_FOR_RESET, pf->state);
|
2018-09-19 17:23:11 -07:00
|
|
|
clear_bit(__ICE_PFR_REQ, pf->state);
|
|
|
|
clear_bit(__ICE_CORER_REQ, pf->state);
|
|
|
|
clear_bit(__ICE_GLOBR_REQ, pf->state);
|
2019-02-08 12:50:56 -08:00
|
|
|
ice_reset_all_vfs(pf, true);
|
2018-08-09 06:29:47 -07:00
|
|
|
}
|
2018-08-09 06:29:50 -07:00
|
|
|
|
|
|
|
return;
|
2018-03-20 07:58:18 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/* No pending resets to finish processing. Check for new resets */
|
2018-09-19 17:23:11 -07:00
|
|
|
if (test_bit(__ICE_PFR_REQ, pf->state))
|
2018-08-09 06:29:50 -07:00
|
|
|
reset_type = ICE_RESET_PFR;
|
2018-09-19 17:23:11 -07:00
|
|
|
if (test_bit(__ICE_CORER_REQ, pf->state))
|
2018-08-09 06:29:50 -07:00
|
|
|
reset_type = ICE_RESET_CORER;
|
2018-09-19 17:23:11 -07:00
|
|
|
if (test_bit(__ICE_GLOBR_REQ, pf->state))
|
2018-03-20 07:58:18 -07:00
|
|
|
reset_type = ICE_RESET_GLOBR;
|
2018-08-09 06:29:50 -07:00
|
|
|
/* If no valid reset type requested just return */
|
|
|
|
if (reset_type == ICE_RESET_INVAL)
|
|
|
|
return;
|
2018-03-20 07:58:18 -07:00
|
|
|
|
2018-08-09 06:29:50 -07:00
|
|
|
/* reset if not already down or busy */
|
2018-03-20 07:58:18 -07:00
|
|
|
if (!test_bit(__ICE_DOWN, pf->state) &&
|
|
|
|
!test_bit(__ICE_CFG_BUSY, pf->state)) {
|
|
|
|
ice_do_reset(pf, reset_type);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:13 -07:00
|
|
|
/**
|
|
|
|
* ice_print_link_msg - print link up or down message
|
|
|
|
* @vsi: the VSI whose link status is being queried
|
|
|
|
* @isup: boolean for if the link is now up or down
|
|
|
|
*/
|
2018-03-20 07:58:16 -07:00
|
|
|
void ice_print_link_msg(struct ice_vsi *vsi, bool isup)
|
2018-03-20 07:58:13 -07:00
|
|
|
{
|
|
|
|
const char *speed;
|
|
|
|
const char *fc;
|
|
|
|
|
2019-02-28 15:26:01 -08:00
|
|
|
if (!vsi)
|
|
|
|
return;
|
|
|
|
|
2018-03-20 07:58:13 -07:00
|
|
|
if (vsi->current_isup == isup)
|
|
|
|
return;
|
|
|
|
|
|
|
|
vsi->current_isup = isup;
|
|
|
|
|
|
|
|
if (!isup) {
|
|
|
|
netdev_info(vsi->netdev, "NIC Link is Down\n");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (vsi->port_info->phy.link_info.link_speed) {
|
|
|
|
case ICE_AQ_LINK_SPEED_40GB:
|
|
|
|
speed = "40 G";
|
|
|
|
break;
|
|
|
|
case ICE_AQ_LINK_SPEED_25GB:
|
|
|
|
speed = "25 G";
|
|
|
|
break;
|
|
|
|
case ICE_AQ_LINK_SPEED_20GB:
|
|
|
|
speed = "20 G";
|
|
|
|
break;
|
|
|
|
case ICE_AQ_LINK_SPEED_10GB:
|
|
|
|
speed = "10 G";
|
|
|
|
break;
|
|
|
|
case ICE_AQ_LINK_SPEED_5GB:
|
|
|
|
speed = "5 G";
|
|
|
|
break;
|
|
|
|
case ICE_AQ_LINK_SPEED_2500MB:
|
|
|
|
speed = "2.5 G";
|
|
|
|
break;
|
|
|
|
case ICE_AQ_LINK_SPEED_1000MB:
|
|
|
|
speed = "1 G";
|
|
|
|
break;
|
|
|
|
case ICE_AQ_LINK_SPEED_100MB:
|
|
|
|
speed = "100 M";
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
speed = "Unknown";
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (vsi->port_info->fc.current_mode) {
|
|
|
|
case ICE_FC_FULL:
|
|
|
|
fc = "RX/TX";
|
|
|
|
break;
|
|
|
|
case ICE_FC_TX_PAUSE:
|
|
|
|
fc = "TX";
|
|
|
|
break;
|
|
|
|
case ICE_FC_RX_PAUSE:
|
|
|
|
fc = "RX";
|
|
|
|
break;
|
2019-02-19 15:04:06 -08:00
|
|
|
case ICE_FC_NONE:
|
|
|
|
fc = "None";
|
|
|
|
break;
|
2018-03-20 07:58:13 -07:00
|
|
|
default:
|
|
|
|
fc = "Unknown";
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
netdev_info(vsi->netdev, "NIC Link is up %sbps, Flow Control: %s\n",
|
|
|
|
speed, fc);
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:18 -07:00
|
|
|
/**
|
2019-02-19 15:04:13 -08:00
|
|
|
* ice_vsi_link_event - update the VSI's netdev
|
|
|
|
* @vsi: the VSI on which the link event occurred
|
|
|
|
* @link_up: whether or not the VSI needs to be set up or down
|
2018-03-20 07:58:18 -07:00
|
|
|
*/
|
|
|
|
static void ice_vsi_link_event(struct ice_vsi *vsi, bool link_up)
|
|
|
|
{
|
2019-02-28 15:26:01 -08:00
|
|
|
if (!vsi)
|
|
|
|
return;
|
|
|
|
|
|
|
|
if (test_bit(__ICE_DOWN, vsi->state) || !vsi->netdev)
|
2018-03-20 07:58:18 -07:00
|
|
|
return;
|
|
|
|
|
|
|
|
if (vsi->type == ICE_VSI_PF) {
|
2019-02-28 15:26:01 -08:00
|
|
|
if (link_up == netif_carrier_ok(vsi->netdev))
|
2018-03-20 07:58:18 -07:00
|
|
|
return;
|
2019-02-28 15:26:01 -08:00
|
|
|
|
2018-03-20 07:58:18 -07:00
|
|
|
if (link_up) {
|
|
|
|
netif_carrier_on(vsi->netdev);
|
|
|
|
netif_tx_wake_all_queues(vsi->netdev);
|
|
|
|
} else {
|
|
|
|
netif_carrier_off(vsi->netdev);
|
|
|
|
netif_tx_stop_all_queues(vsi->netdev);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_link_event - process the link event
|
|
|
|
* @pf: pf that the link event is associated with
|
|
|
|
* @pi: port_info for the port that the link event is associated with
|
2019-02-28 15:26:01 -08:00
|
|
|
* @link_up: true if the physical link is up and false if it is down
|
|
|
|
* @link_speed: current link speed received from the link event
|
2018-03-20 07:58:18 -07:00
|
|
|
*
|
2019-02-28 15:26:01 -08:00
|
|
|
* Returns 0 on success and negative on failure
|
2018-03-20 07:58:18 -07:00
|
|
|
*/
|
|
|
|
static int
|
2019-02-28 15:26:01 -08:00
|
|
|
ice_link_event(struct ice_pf *pf, struct ice_port_info *pi, bool link_up,
|
|
|
|
u16 link_speed)
|
2018-03-20 07:58:18 -07:00
|
|
|
{
|
|
|
|
struct ice_phy_info *phy_info;
|
2019-02-28 15:26:01 -08:00
|
|
|
struct ice_vsi *vsi;
|
|
|
|
u16 old_link_speed;
|
|
|
|
bool old_link;
|
|
|
|
int result;
|
2018-03-20 07:58:18 -07:00
|
|
|
|
|
|
|
phy_info = &pi->phy;
|
|
|
|
phy_info->link_info_old = phy_info->link_info;
|
|
|
|
|
2019-02-28 15:26:01 -08:00
|
|
|
old_link = !!(phy_info->link_info_old.link_info & ICE_AQ_LINK_UP);
|
2018-03-20 07:58:18 -07:00
|
|
|
old_link_speed = phy_info->link_info_old.link_speed;
|
|
|
|
|
2019-02-28 15:26:01 -08:00
|
|
|
/* update the link info structures and re-enable link events,
|
|
|
|
* don't bail on failure due to other book keeping needed
|
|
|
|
*/
|
|
|
|
result = ice_update_link_info(pi);
|
|
|
|
if (result)
|
2018-03-20 07:58:18 -07:00
|
|
|
dev_dbg(&pf->pdev->dev,
|
2019-02-28 15:26:01 -08:00
|
|
|
"Failed to update link status and re-enable link events for port %d\n",
|
|
|
|
pi->lport);
|
2018-03-20 07:58:18 -07:00
|
|
|
|
2019-02-28 15:26:01 -08:00
|
|
|
/* if the old link up/down and speed is the same as the new */
|
|
|
|
if (link_up == old_link && link_speed == old_link_speed)
|
|
|
|
return result;
|
2018-03-20 07:58:18 -07:00
|
|
|
|
2019-02-28 15:26:01 -08:00
|
|
|
vsi = ice_find_vsi_by_type(pf, ICE_VSI_PF);
|
|
|
|
if (!vsi || !vsi->port_info)
|
|
|
|
return -EINVAL;
|
2018-03-20 07:58:18 -07:00
|
|
|
|
2019-02-28 15:26:01 -08:00
|
|
|
ice_vsi_link_event(vsi, link_up);
|
|
|
|
ice_print_link_msg(vsi, link_up);
|
2018-03-20 07:58:18 -07:00
|
|
|
|
2019-02-28 15:26:01 -08:00
|
|
|
if (pf->num_alloc_vfs)
|
2019-02-08 12:50:37 -08:00
|
|
|
ice_vc_notify_link_state(pf);
|
2018-09-19 17:43:00 -07:00
|
|
|
|
2019-02-28 15:26:01 -08:00
|
|
|
return result;
|
2018-03-20 07:58:18 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2018-10-18 08:37:09 -07:00
|
|
|
* ice_watchdog_subtask - periodic tasks not using event driven scheduling
|
|
|
|
* @pf: board private structure
|
2018-03-20 07:58:18 -07:00
|
|
|
*/
|
2018-10-18 08:37:09 -07:00
|
|
|
static void ice_watchdog_subtask(struct ice_pf *pf)
|
2018-03-20 07:58:18 -07:00
|
|
|
{
|
2018-10-18 08:37:09 -07:00
|
|
|
int i;
|
2018-03-20 07:58:18 -07:00
|
|
|
|
2018-10-18 08:37:09 -07:00
|
|
|
/* if interface is down do nothing */
|
|
|
|
if (test_bit(__ICE_DOWN, pf->state) ||
|
|
|
|
test_bit(__ICE_CFG_BUSY, pf->state))
|
|
|
|
return;
|
2018-03-20 07:58:18 -07:00
|
|
|
|
2018-10-18 08:37:09 -07:00
|
|
|
/* make sure we don't do these things too often */
|
|
|
|
if (time_before(jiffies,
|
|
|
|
pf->serv_tmr_prev + pf->serv_tmr_period))
|
|
|
|
return;
|
2018-03-20 07:58:18 -07:00
|
|
|
|
2018-10-18 08:37:09 -07:00
|
|
|
pf->serv_tmr_prev = jiffies;
|
|
|
|
|
|
|
|
/* Update the stats for active netdevs so the network stack
|
|
|
|
* can look at updated numbers whenever it cares to
|
|
|
|
*/
|
|
|
|
ice_update_pf_stats(pf);
|
2019-02-08 12:50:54 -08:00
|
|
|
ice_for_each_vsi(pf, i)
|
2018-10-18 08:37:09 -07:00
|
|
|
if (pf->vsi[i] && pf->vsi[i]->netdev)
|
|
|
|
ice_update_vsi_stats(pf->vsi[i]);
|
2018-03-20 07:58:18 -07:00
|
|
|
}
|
|
|
|
|
2019-02-26 16:35:23 -08:00
|
|
|
/**
|
|
|
|
* ice_init_link_events - enable/initialize link events
|
|
|
|
* @pi: pointer to the port_info instance
|
|
|
|
*
|
|
|
|
* Returns -EIO on failure, 0 on success
|
|
|
|
*/
|
|
|
|
static int ice_init_link_events(struct ice_port_info *pi)
|
|
|
|
{
|
|
|
|
u16 mask;
|
|
|
|
|
|
|
|
mask = ~((u16)(ICE_AQ_LINK_EVENT_UPDOWN | ICE_AQ_LINK_EVENT_MEDIA_NA |
|
|
|
|
ICE_AQ_LINK_EVENT_MODULE_QUAL_FAIL));
|
|
|
|
|
|
|
|
if (ice_aq_set_event_mask(pi->hw, pi->lport, mask, NULL)) {
|
|
|
|
dev_dbg(ice_hw_to_dev(pi->hw),
|
|
|
|
"Failed to set link event mask for port %d\n",
|
|
|
|
pi->lport);
|
|
|
|
return -EIO;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (ice_aq_get_link_info(pi, true, NULL, NULL)) {
|
|
|
|
dev_dbg(ice_hw_to_dev(pi->hw),
|
|
|
|
"Failed to enable link events for port %d\n",
|
|
|
|
pi->lport);
|
|
|
|
return -EIO;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_handle_link_event - handle link event via ARQ
|
|
|
|
* @pf: pf that the link event is associated with
|
2019-02-28 15:26:01 -08:00
|
|
|
* @event: event structure containing link status info
|
2019-02-26 16:35:23 -08:00
|
|
|
*/
|
2019-02-28 15:26:01 -08:00
|
|
|
static int
|
|
|
|
ice_handle_link_event(struct ice_pf *pf, struct ice_rq_event_info *event)
|
2019-02-26 16:35:23 -08:00
|
|
|
{
|
2019-02-28 15:26:01 -08:00
|
|
|
struct ice_aqc_get_link_status_data *link_data;
|
2019-02-26 16:35:23 -08:00
|
|
|
struct ice_port_info *port_info;
|
|
|
|
int status;
|
|
|
|
|
2019-02-28 15:26:01 -08:00
|
|
|
link_data = (struct ice_aqc_get_link_status_data *)event->msg_buf;
|
2019-02-26 16:35:23 -08:00
|
|
|
port_info = pf->hw.port_info;
|
|
|
|
if (!port_info)
|
|
|
|
return -EINVAL;
|
|
|
|
|
2019-02-28 15:26:01 -08:00
|
|
|
status = ice_link_event(pf, port_info,
|
|
|
|
!!(link_data->link_info & ICE_AQ_LINK_UP),
|
|
|
|
le16_to_cpu(link_data->link_speed));
|
2019-02-26 16:35:23 -08:00
|
|
|
if (status)
|
|
|
|
dev_dbg(&pf->pdev->dev,
|
|
|
|
"Could not process link event, error %d\n", status);
|
|
|
|
|
|
|
|
return status;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
/**
|
|
|
|
* __ice_clean_ctrlq - helper function to clean controlq rings
|
|
|
|
* @pf: ptr to struct ice_pf
|
|
|
|
* @q_type: specific Control queue type
|
|
|
|
*/
|
|
|
|
static int __ice_clean_ctrlq(struct ice_pf *pf, enum ice_ctl_q q_type)
|
|
|
|
{
|
|
|
|
struct ice_rq_event_info event;
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
struct ice_ctl_q_info *cq;
|
|
|
|
u16 pending, i = 0;
|
|
|
|
const char *qtype;
|
|
|
|
u32 oldval, val;
|
|
|
|
|
2018-03-20 07:58:18 -07:00
|
|
|
/* Do not clean control queue if/when PF reset fails */
|
|
|
|
if (test_bit(__ICE_RESET_FAILED, pf->state))
|
|
|
|
return 0;
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
switch (q_type) {
|
|
|
|
case ICE_CTL_Q_ADMIN:
|
|
|
|
cq = &hw->adminq;
|
|
|
|
qtype = "Admin";
|
|
|
|
break;
|
2018-09-19 17:42:54 -07:00
|
|
|
case ICE_CTL_Q_MAILBOX:
|
|
|
|
cq = &hw->mailboxq;
|
|
|
|
qtype = "Mailbox";
|
|
|
|
break;
|
2018-03-20 07:58:10 -07:00
|
|
|
default:
|
|
|
|
dev_warn(&pf->pdev->dev, "Unknown control queue type 0x%x\n",
|
|
|
|
q_type);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* check for error indications - PF_xx_AxQLEN register layout for
|
|
|
|
* FW/MBX/SB are identical so just use defines for PF_FW_AxQLEN.
|
|
|
|
*/
|
|
|
|
val = rd32(hw, cq->rq.len);
|
|
|
|
if (val & (PF_FW_ARQLEN_ARQVFE_M | PF_FW_ARQLEN_ARQOVFL_M |
|
|
|
|
PF_FW_ARQLEN_ARQCRIT_M)) {
|
|
|
|
oldval = val;
|
|
|
|
if (val & PF_FW_ARQLEN_ARQVFE_M)
|
|
|
|
dev_dbg(&pf->pdev->dev,
|
|
|
|
"%s Receive Queue VF Error detected\n", qtype);
|
|
|
|
if (val & PF_FW_ARQLEN_ARQOVFL_M) {
|
|
|
|
dev_dbg(&pf->pdev->dev,
|
|
|
|
"%s Receive Queue Overflow Error detected\n",
|
|
|
|
qtype);
|
|
|
|
}
|
|
|
|
if (val & PF_FW_ARQLEN_ARQCRIT_M)
|
|
|
|
dev_dbg(&pf->pdev->dev,
|
|
|
|
"%s Receive Queue Critical Error detected\n",
|
|
|
|
qtype);
|
|
|
|
val &= ~(PF_FW_ARQLEN_ARQVFE_M | PF_FW_ARQLEN_ARQOVFL_M |
|
|
|
|
PF_FW_ARQLEN_ARQCRIT_M);
|
|
|
|
if (oldval != val)
|
|
|
|
wr32(hw, cq->rq.len, val);
|
|
|
|
}
|
|
|
|
|
|
|
|
val = rd32(hw, cq->sq.len);
|
|
|
|
if (val & (PF_FW_ATQLEN_ATQVFE_M | PF_FW_ATQLEN_ATQOVFL_M |
|
|
|
|
PF_FW_ATQLEN_ATQCRIT_M)) {
|
|
|
|
oldval = val;
|
|
|
|
if (val & PF_FW_ATQLEN_ATQVFE_M)
|
|
|
|
dev_dbg(&pf->pdev->dev,
|
|
|
|
"%s Send Queue VF Error detected\n", qtype);
|
|
|
|
if (val & PF_FW_ATQLEN_ATQOVFL_M) {
|
|
|
|
dev_dbg(&pf->pdev->dev,
|
|
|
|
"%s Send Queue Overflow Error detected\n",
|
|
|
|
qtype);
|
|
|
|
}
|
|
|
|
if (val & PF_FW_ATQLEN_ATQCRIT_M)
|
|
|
|
dev_dbg(&pf->pdev->dev,
|
|
|
|
"%s Send Queue Critical Error detected\n",
|
|
|
|
qtype);
|
|
|
|
val &= ~(PF_FW_ATQLEN_ATQVFE_M | PF_FW_ATQLEN_ATQOVFL_M |
|
|
|
|
PF_FW_ATQLEN_ATQCRIT_M);
|
|
|
|
if (oldval != val)
|
|
|
|
wr32(hw, cq->sq.len, val);
|
|
|
|
}
|
|
|
|
|
|
|
|
event.buf_len = cq->rq_buf_size;
|
|
|
|
event.msg_buf = devm_kzalloc(&pf->pdev->dev, event.buf_len,
|
|
|
|
GFP_KERNEL);
|
|
|
|
if (!event.msg_buf)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
do {
|
|
|
|
enum ice_status ret;
|
2018-03-20 07:58:18 -07:00
|
|
|
u16 opcode;
|
2018-03-20 07:58:10 -07:00
|
|
|
|
|
|
|
ret = ice_clean_rq_elem(hw, cq, &event, &pending);
|
|
|
|
if (ret == ICE_ERR_AQ_NO_WORK)
|
|
|
|
break;
|
|
|
|
if (ret) {
|
|
|
|
dev_err(&pf->pdev->dev,
|
|
|
|
"%s Receive Queue event error %d\n", qtype,
|
|
|
|
ret);
|
|
|
|
break;
|
|
|
|
}
|
2018-03-20 07:58:18 -07:00
|
|
|
|
|
|
|
opcode = le16_to_cpu(event.desc.opcode);
|
|
|
|
|
|
|
|
switch (opcode) {
|
2019-02-26 16:35:23 -08:00
|
|
|
case ice_aqc_opc_get_link_status:
|
2019-02-28 15:26:01 -08:00
|
|
|
if (ice_handle_link_event(pf, &event))
|
2019-02-26 16:35:23 -08:00
|
|
|
dev_err(&pf->pdev->dev,
|
|
|
|
"Could not handle link event\n");
|
|
|
|
break;
|
2018-09-19 17:42:59 -07:00
|
|
|
case ice_mbx_opc_send_msg_to_pf:
|
|
|
|
ice_vc_process_vf_msg(pf, &event);
|
|
|
|
break;
|
2018-08-09 06:29:55 -07:00
|
|
|
case ice_aqc_opc_fw_logging:
|
|
|
|
ice_output_fw_log(hw, &event.desc, event.msg_buf);
|
|
|
|
break;
|
2019-02-28 15:24:26 -08:00
|
|
|
case ice_aqc_opc_lldp_set_mib_change:
|
|
|
|
ice_dcb_process_lldp_set_mib_change(pf, &event);
|
|
|
|
break;
|
2018-03-20 07:58:18 -07:00
|
|
|
default:
|
|
|
|
dev_dbg(&pf->pdev->dev,
|
|
|
|
"%s Receive Queue unknown event 0x%04x ignored\n",
|
|
|
|
qtype, opcode);
|
|
|
|
break;
|
|
|
|
}
|
2018-03-20 07:58:10 -07:00
|
|
|
} while (pending && (i++ < ICE_DFLT_IRQ_WORK));
|
|
|
|
|
|
|
|
devm_kfree(&pf->pdev->dev, event.msg_buf);
|
|
|
|
|
|
|
|
return pending && (i == ICE_DFLT_IRQ_WORK);
|
|
|
|
}
|
|
|
|
|
2018-08-09 06:28:56 -07:00
|
|
|
/**
|
|
|
|
* ice_ctrlq_pending - check if there is a difference between ntc and ntu
|
|
|
|
* @hw: pointer to hardware info
|
|
|
|
* @cq: control queue information
|
|
|
|
*
|
|
|
|
* returns true if there are pending messages in a queue, false if there aren't
|
|
|
|
*/
|
|
|
|
static bool ice_ctrlq_pending(struct ice_hw *hw, struct ice_ctl_q_info *cq)
|
|
|
|
{
|
|
|
|
u16 ntu;
|
|
|
|
|
|
|
|
ntu = (u16)(rd32(hw, cq->rq.head) & cq->rq.head_mask);
|
|
|
|
return cq->rq.next_to_clean != ntu;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
/**
|
|
|
|
* ice_clean_adminq_subtask - clean the AdminQ rings
|
|
|
|
* @pf: board private structure
|
|
|
|
*/
|
|
|
|
static void ice_clean_adminq_subtask(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
|
|
|
|
if (!test_bit(__ICE_ADMINQ_EVENT_PENDING, pf->state))
|
|
|
|
return;
|
|
|
|
|
|
|
|
if (__ice_clean_ctrlq(pf, ICE_CTL_Q_ADMIN))
|
|
|
|
return;
|
|
|
|
|
|
|
|
clear_bit(__ICE_ADMINQ_EVENT_PENDING, pf->state);
|
|
|
|
|
2018-08-09 06:28:56 -07:00
|
|
|
/* There might be a situation where new messages arrive to a control
|
|
|
|
* queue between processing the last message and clearing the
|
|
|
|
* EVENT_PENDING bit. So before exiting, check queue head again (using
|
|
|
|
* ice_ctrlq_pending) and process new messages if any.
|
|
|
|
*/
|
|
|
|
if (ice_ctrlq_pending(hw, &hw->adminq))
|
|
|
|
__ice_clean_ctrlq(pf, ICE_CTL_Q_ADMIN);
|
2018-03-20 07:58:10 -07:00
|
|
|
|
|
|
|
ice_flush(hw);
|
|
|
|
}
|
|
|
|
|
2018-09-19 17:42:54 -07:00
|
|
|
/**
|
|
|
|
* ice_clean_mailboxq_subtask - clean the MailboxQ rings
|
|
|
|
* @pf: board private structure
|
|
|
|
*/
|
|
|
|
static void ice_clean_mailboxq_subtask(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
|
|
|
|
if (!test_bit(__ICE_MAILBOXQ_EVENT_PENDING, pf->state))
|
|
|
|
return;
|
|
|
|
|
|
|
|
if (__ice_clean_ctrlq(pf, ICE_CTL_Q_MAILBOX))
|
|
|
|
return;
|
|
|
|
|
|
|
|
clear_bit(__ICE_MAILBOXQ_EVENT_PENDING, pf->state);
|
|
|
|
|
|
|
|
if (ice_ctrlq_pending(hw, &hw->mailboxq))
|
|
|
|
__ice_clean_ctrlq(pf, ICE_CTL_Q_MAILBOX);
|
|
|
|
|
|
|
|
ice_flush(hw);
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
/**
|
|
|
|
* ice_service_task_schedule - schedule the service task to wake up
|
|
|
|
* @pf: board private structure
|
|
|
|
*
|
|
|
|
* If not already scheduled, this puts the task into the work queue.
|
|
|
|
*/
|
|
|
|
static void ice_service_task_schedule(struct ice_pf *pf)
|
|
|
|
{
|
2018-08-09 06:29:57 -07:00
|
|
|
if (!test_bit(__ICE_SERVICE_DIS, pf->state) &&
|
2018-08-09 06:29:50 -07:00
|
|
|
!test_and_set_bit(__ICE_SERVICE_SCHED, pf->state) &&
|
|
|
|
!test_bit(__ICE_NEEDS_RESTART, pf->state))
|
2018-03-20 07:58:10 -07:00
|
|
|
queue_work(ice_wq, &pf->serv_task);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_service_task_complete - finish up the service task
|
|
|
|
* @pf: board private structure
|
|
|
|
*/
|
|
|
|
static void ice_service_task_complete(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
WARN_ON(!test_bit(__ICE_SERVICE_SCHED, pf->state));
|
|
|
|
|
|
|
|
/* force memory (pf->state) to sync before next service task */
|
|
|
|
smp_mb__before_atomic();
|
|
|
|
clear_bit(__ICE_SERVICE_SCHED, pf->state);
|
|
|
|
}
|
|
|
|
|
2018-08-09 06:29:57 -07:00
|
|
|
/**
|
|
|
|
* ice_service_task_stop - stop service task and cancel works
|
|
|
|
* @pf: board private structure
|
|
|
|
*/
|
|
|
|
static void ice_service_task_stop(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
set_bit(__ICE_SERVICE_DIS, pf->state);
|
|
|
|
|
|
|
|
if (pf->serv_tmr.function)
|
|
|
|
del_timer_sync(&pf->serv_tmr);
|
|
|
|
if (pf->serv_task.func)
|
|
|
|
cancel_work_sync(&pf->serv_task);
|
|
|
|
|
|
|
|
clear_bit(__ICE_SERVICE_SCHED, pf->state);
|
|
|
|
}
|
|
|
|
|
2019-02-13 10:51:15 -08:00
|
|
|
/**
|
|
|
|
* ice_service_task_restart - restart service task and schedule works
|
|
|
|
* @pf: board private structure
|
|
|
|
*
|
|
|
|
* This function is needed for suspend and resume works (e.g WoL scenario)
|
|
|
|
*/
|
|
|
|
static void ice_service_task_restart(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
clear_bit(__ICE_SERVICE_DIS, pf->state);
|
|
|
|
ice_service_task_schedule(pf);
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
/**
|
|
|
|
* ice_service_timer - timer callback to schedule service task
|
|
|
|
* @t: pointer to timer_list
|
|
|
|
*/
|
|
|
|
static void ice_service_timer(struct timer_list *t)
|
|
|
|
{
|
|
|
|
struct ice_pf *pf = from_timer(pf, t, serv_tmr);
|
|
|
|
|
|
|
|
mod_timer(&pf->serv_tmr, round_jiffies(pf->serv_tmr_period + jiffies));
|
|
|
|
ice_service_task_schedule(pf);
|
|
|
|
}
|
|
|
|
|
2018-08-09 06:29:53 -07:00
|
|
|
/**
|
|
|
|
* ice_handle_mdd_event - handle malicious driver detect event
|
|
|
|
* @pf: pointer to the PF structure
|
|
|
|
*
|
|
|
|
* Called from service task. OICR interrupt handler indicates MDD event
|
|
|
|
*/
|
|
|
|
static void ice_handle_mdd_event(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
bool mdd_detected = false;
|
|
|
|
u32 reg;
|
2018-09-19 17:43:01 -07:00
|
|
|
int i;
|
2018-08-09 06:29:53 -07:00
|
|
|
|
2019-02-28 15:25:58 -08:00
|
|
|
if (!test_and_clear_bit(__ICE_MDD_EVENT_PENDING, pf->state))
|
2018-08-09 06:29:53 -07:00
|
|
|
return;
|
|
|
|
|
|
|
|
/* find what triggered the MDD event */
|
|
|
|
reg = rd32(hw, GL_MDET_TX_PQM);
|
|
|
|
if (reg & GL_MDET_TX_PQM_VALID_M) {
|
|
|
|
u8 pf_num = (reg & GL_MDET_TX_PQM_PF_NUM_M) >>
|
|
|
|
GL_MDET_TX_PQM_PF_NUM_S;
|
|
|
|
u16 vf_num = (reg & GL_MDET_TX_PQM_VF_NUM_M) >>
|
|
|
|
GL_MDET_TX_PQM_VF_NUM_S;
|
|
|
|
u8 event = (reg & GL_MDET_TX_PQM_MAL_TYPE_M) >>
|
|
|
|
GL_MDET_TX_PQM_MAL_TYPE_S;
|
|
|
|
u16 queue = ((reg & GL_MDET_TX_PQM_QNUM_M) >>
|
|
|
|
GL_MDET_TX_PQM_QNUM_S);
|
|
|
|
|
|
|
|
if (netif_msg_tx_err(pf))
|
|
|
|
dev_info(&pf->pdev->dev, "Malicious Driver Detection event %d on TX queue %d PF# %d VF# %d\n",
|
|
|
|
event, queue, pf_num, vf_num);
|
|
|
|
wr32(hw, GL_MDET_TX_PQM, 0xffffffff);
|
|
|
|
mdd_detected = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
reg = rd32(hw, GL_MDET_TX_TCLAN);
|
|
|
|
if (reg & GL_MDET_TX_TCLAN_VALID_M) {
|
|
|
|
u8 pf_num = (reg & GL_MDET_TX_TCLAN_PF_NUM_M) >>
|
|
|
|
GL_MDET_TX_TCLAN_PF_NUM_S;
|
|
|
|
u16 vf_num = (reg & GL_MDET_TX_TCLAN_VF_NUM_M) >>
|
|
|
|
GL_MDET_TX_TCLAN_VF_NUM_S;
|
|
|
|
u8 event = (reg & GL_MDET_TX_TCLAN_MAL_TYPE_M) >>
|
|
|
|
GL_MDET_TX_TCLAN_MAL_TYPE_S;
|
|
|
|
u16 queue = ((reg & GL_MDET_TX_TCLAN_QNUM_M) >>
|
|
|
|
GL_MDET_TX_TCLAN_QNUM_S);
|
|
|
|
|
|
|
|
if (netif_msg_rx_err(pf))
|
|
|
|
dev_info(&pf->pdev->dev, "Malicious Driver Detection event %d on TX queue %d PF# %d VF# %d\n",
|
|
|
|
event, queue, pf_num, vf_num);
|
|
|
|
wr32(hw, GL_MDET_TX_TCLAN, 0xffffffff);
|
|
|
|
mdd_detected = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
reg = rd32(hw, GL_MDET_RX);
|
|
|
|
if (reg & GL_MDET_RX_VALID_M) {
|
|
|
|
u8 pf_num = (reg & GL_MDET_RX_PF_NUM_M) >>
|
|
|
|
GL_MDET_RX_PF_NUM_S;
|
|
|
|
u16 vf_num = (reg & GL_MDET_RX_VF_NUM_M) >>
|
|
|
|
GL_MDET_RX_VF_NUM_S;
|
|
|
|
u8 event = (reg & GL_MDET_RX_MAL_TYPE_M) >>
|
|
|
|
GL_MDET_RX_MAL_TYPE_S;
|
|
|
|
u16 queue = ((reg & GL_MDET_RX_QNUM_M) >>
|
|
|
|
GL_MDET_RX_QNUM_S);
|
|
|
|
|
|
|
|
if (netif_msg_rx_err(pf))
|
|
|
|
dev_info(&pf->pdev->dev, "Malicious Driver Detection event %d on RX queue %d PF# %d VF# %d\n",
|
|
|
|
event, queue, pf_num, vf_num);
|
|
|
|
wr32(hw, GL_MDET_RX, 0xffffffff);
|
|
|
|
mdd_detected = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (mdd_detected) {
|
|
|
|
bool pf_mdd_detected = false;
|
|
|
|
|
|
|
|
reg = rd32(hw, PF_MDET_TX_PQM);
|
|
|
|
if (reg & PF_MDET_TX_PQM_VALID_M) {
|
|
|
|
wr32(hw, PF_MDET_TX_PQM, 0xFFFF);
|
|
|
|
dev_info(&pf->pdev->dev, "TX driver issue detected, PF reset issued\n");
|
|
|
|
pf_mdd_detected = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
reg = rd32(hw, PF_MDET_TX_TCLAN);
|
|
|
|
if (reg & PF_MDET_TX_TCLAN_VALID_M) {
|
|
|
|
wr32(hw, PF_MDET_TX_TCLAN, 0xFFFF);
|
|
|
|
dev_info(&pf->pdev->dev, "TX driver issue detected, PF reset issued\n");
|
|
|
|
pf_mdd_detected = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
reg = rd32(hw, PF_MDET_RX);
|
|
|
|
if (reg & PF_MDET_RX_VALID_M) {
|
|
|
|
wr32(hw, PF_MDET_RX, 0xFFFF);
|
|
|
|
dev_info(&pf->pdev->dev, "RX driver issue detected, PF reset issued\n");
|
|
|
|
pf_mdd_detected = true;
|
|
|
|
}
|
|
|
|
/* Queue belongs to the PF initiate a reset */
|
|
|
|
if (pf_mdd_detected) {
|
|
|
|
set_bit(__ICE_NEEDS_RESTART, pf->state);
|
|
|
|
ice_service_task_schedule(pf);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2019-04-16 10:30:45 -07:00
|
|
|
/* check to see if one of the VFs caused the MDD */
|
|
|
|
for (i = 0; i < pf->num_alloc_vfs; i++) {
|
2018-09-19 17:43:01 -07:00
|
|
|
struct ice_vf *vf = &pf->vf[i];
|
|
|
|
|
2019-04-16 10:30:45 -07:00
|
|
|
bool vf_mdd_detected = false;
|
2019-04-16 10:21:14 -07:00
|
|
|
|
2018-09-19 17:43:01 -07:00
|
|
|
reg = rd32(hw, VP_MDET_TX_PQM(i));
|
|
|
|
if (reg & VP_MDET_TX_PQM_VALID_M) {
|
|
|
|
wr32(hw, VP_MDET_TX_PQM(i), 0xFFFF);
|
2019-04-16 10:30:45 -07:00
|
|
|
vf_mdd_detected = true;
|
2018-09-19 17:43:01 -07:00
|
|
|
dev_info(&pf->pdev->dev, "TX driver issue detected on VF %d\n",
|
|
|
|
i);
|
|
|
|
}
|
|
|
|
|
|
|
|
reg = rd32(hw, VP_MDET_TX_TCLAN(i));
|
|
|
|
if (reg & VP_MDET_TX_TCLAN_VALID_M) {
|
|
|
|
wr32(hw, VP_MDET_TX_TCLAN(i), 0xFFFF);
|
2019-04-16 10:30:45 -07:00
|
|
|
vf_mdd_detected = true;
|
2018-09-19 17:43:01 -07:00
|
|
|
dev_info(&pf->pdev->dev, "TX driver issue detected on VF %d\n",
|
|
|
|
i);
|
|
|
|
}
|
|
|
|
|
|
|
|
reg = rd32(hw, VP_MDET_TX_TDPU(i));
|
|
|
|
if (reg & VP_MDET_TX_TDPU_VALID_M) {
|
|
|
|
wr32(hw, VP_MDET_TX_TDPU(i), 0xFFFF);
|
2019-04-16 10:30:45 -07:00
|
|
|
vf_mdd_detected = true;
|
2018-09-19 17:43:01 -07:00
|
|
|
dev_info(&pf->pdev->dev, "TX driver issue detected on VF %d\n",
|
|
|
|
i);
|
|
|
|
}
|
|
|
|
|
|
|
|
reg = rd32(hw, VP_MDET_RX(i));
|
|
|
|
if (reg & VP_MDET_RX_VALID_M) {
|
|
|
|
wr32(hw, VP_MDET_RX(i), 0xFFFF);
|
2019-04-16 10:30:45 -07:00
|
|
|
vf_mdd_detected = true;
|
2018-09-19 17:43:01 -07:00
|
|
|
dev_info(&pf->pdev->dev, "RX driver issue detected on VF %d\n",
|
|
|
|
i);
|
|
|
|
}
|
|
|
|
|
2019-04-16 10:30:45 -07:00
|
|
|
if (vf_mdd_detected) {
|
2019-04-16 10:21:14 -07:00
|
|
|
vf->num_mdd_events++;
|
2019-04-16 10:30:45 -07:00
|
|
|
if (vf->num_mdd_events > 1)
|
|
|
|
dev_info(&pf->pdev->dev, "VF %d has had %llu MDD events since last boot\n",
|
|
|
|
i, vf->num_mdd_events);
|
2018-09-19 17:43:01 -07:00
|
|
|
}
|
|
|
|
}
|
2018-08-09 06:29:53 -07:00
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
/**
|
|
|
|
* ice_service_task - manage and run subtasks
|
|
|
|
* @work: pointer to work_struct contained by the PF struct
|
|
|
|
*/
|
|
|
|
static void ice_service_task(struct work_struct *work)
|
|
|
|
{
|
|
|
|
struct ice_pf *pf = container_of(work, struct ice_pf, serv_task);
|
|
|
|
unsigned long start_time = jiffies;
|
|
|
|
|
|
|
|
/* subtasks */
|
2018-03-20 07:58:18 -07:00
|
|
|
|
|
|
|
/* process reset requests first */
|
|
|
|
ice_reset_subtask(pf);
|
|
|
|
|
2018-08-09 06:29:50 -07:00
|
|
|
/* bail if a reset/recovery cycle is pending or rebuild failed */
|
2018-09-19 17:23:11 -07:00
|
|
|
if (ice_is_reset_in_progress(pf->state) ||
|
2018-08-09 06:29:50 -07:00
|
|
|
test_bit(__ICE_SUSPENDED, pf->state) ||
|
|
|
|
test_bit(__ICE_NEEDS_RESTART, pf->state)) {
|
2018-03-20 07:58:18 -07:00
|
|
|
ice_service_task_complete(pf);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2018-08-09 06:29:53 -07:00
|
|
|
ice_check_for_hang_subtask(pf);
|
2018-03-20 07:58:19 -07:00
|
|
|
ice_sync_fltr_subtask(pf);
|
2018-08-09 06:29:53 -07:00
|
|
|
ice_handle_mdd_event(pf);
|
2018-09-19 17:42:57 -07:00
|
|
|
ice_process_vflr_event(pf);
|
2018-03-20 07:58:16 -07:00
|
|
|
ice_watchdog_subtask(pf);
|
2018-03-20 07:58:10 -07:00
|
|
|
ice_clean_adminq_subtask(pf);
|
2018-09-19 17:42:54 -07:00
|
|
|
ice_clean_mailboxq_subtask(pf);
|
2018-03-20 07:58:10 -07:00
|
|
|
|
|
|
|
/* Clear __ICE_SERVICE_SCHED flag to allow scheduling next event */
|
|
|
|
ice_service_task_complete(pf);
|
|
|
|
|
|
|
|
/* If the tasks have taken longer than one service timer period
|
|
|
|
* or there is more work to be done, reset the service timer to
|
|
|
|
* schedule the service task now.
|
|
|
|
*/
|
|
|
|
if (time_after(jiffies, (start_time + pf->serv_tmr_period)) ||
|
2018-08-09 06:29:53 -07:00
|
|
|
test_bit(__ICE_MDD_EVENT_PENDING, pf->state) ||
|
2018-09-19 17:42:57 -07:00
|
|
|
test_bit(__ICE_VFLR_EVENT_PENDING, pf->state) ||
|
2018-09-19 17:42:54 -07:00
|
|
|
test_bit(__ICE_MAILBOXQ_EVENT_PENDING, pf->state) ||
|
2018-03-20 07:58:10 -07:00
|
|
|
test_bit(__ICE_ADMINQ_EVENT_PENDING, pf->state))
|
|
|
|
mod_timer(&pf->serv_tmr, jiffies);
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:07 -07:00
|
|
|
/**
|
|
|
|
* ice_set_ctrlq_len - helper function to set controlq length
|
2019-02-19 15:04:13 -08:00
|
|
|
* @hw: pointer to the HW instance
|
2018-03-20 07:58:07 -07:00
|
|
|
*/
|
|
|
|
static void ice_set_ctrlq_len(struct ice_hw *hw)
|
|
|
|
{
|
|
|
|
hw->adminq.num_rq_entries = ICE_AQ_LEN;
|
|
|
|
hw->adminq.num_sq_entries = ICE_AQ_LEN;
|
|
|
|
hw->adminq.rq_buf_size = ICE_AQ_MAX_BUF_LEN;
|
|
|
|
hw->adminq.sq_buf_size = ICE_AQ_MAX_BUF_LEN;
|
2018-09-19 17:42:54 -07:00
|
|
|
hw->mailboxq.num_rq_entries = ICE_MBXQ_LEN;
|
|
|
|
hw->mailboxq.num_sq_entries = ICE_MBXQ_LEN;
|
|
|
|
hw->mailboxq.rq_buf_size = ICE_MBXQ_MAX_BUF_LEN;
|
|
|
|
hw->mailboxq.sq_buf_size = ICE_MBXQ_MAX_BUF_LEN;
|
2018-03-20 07:58:07 -07:00
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:13 -07:00
|
|
|
/**
|
|
|
|
* ice_irq_affinity_notify - Callback for affinity changes
|
|
|
|
* @notify: context as to what irq was changed
|
|
|
|
* @mask: the new affinity mask
|
|
|
|
*
|
|
|
|
* This is a callback function used by the irq_set_affinity_notifier function
|
|
|
|
* so that we may register to receive changes to the irq affinity masks.
|
|
|
|
*/
|
2019-02-26 16:35:11 -08:00
|
|
|
static void
|
|
|
|
ice_irq_affinity_notify(struct irq_affinity_notify *notify,
|
|
|
|
const cpumask_t *mask)
|
2018-03-20 07:58:13 -07:00
|
|
|
{
|
|
|
|
struct ice_q_vector *q_vector =
|
|
|
|
container_of(notify, struct ice_q_vector, affinity_notify);
|
|
|
|
|
|
|
|
cpumask_copy(&q_vector->affinity_mask, mask);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_irq_affinity_release - Callback for affinity notifier release
|
|
|
|
* @ref: internal core kernel usage
|
|
|
|
*
|
|
|
|
* This is a callback function used by the irq_set_affinity_notifier function
|
|
|
|
* to inform the current notification subscriber that they will no longer
|
|
|
|
* receive notifications.
|
|
|
|
*/
|
|
|
|
static void ice_irq_affinity_release(struct kref __always_unused *ref) {}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_vsi_ena_irq - Enable IRQ for the given VSI
|
|
|
|
* @vsi: the VSI being configured
|
|
|
|
*/
|
|
|
|
static int ice_vsi_ena_irq(struct ice_vsi *vsi)
|
|
|
|
{
|
|
|
|
struct ice_pf *pf = vsi->back;
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
|
|
|
|
if (test_bit(ICE_FLAG_MSIX_ENA, pf->flags)) {
|
|
|
|
int i;
|
|
|
|
|
2019-02-28 15:25:53 -08:00
|
|
|
ice_for_each_q_vector(vsi, i)
|
2018-03-20 07:58:13 -07:00
|
|
|
ice_irq_dynamic_ena(hw, vsi, vsi->q_vectors[i]);
|
|
|
|
}
|
|
|
|
|
|
|
|
ice_flush(hw);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_vsi_req_irq_msix - get MSI-X vectors from the OS for the VSI
|
|
|
|
* @vsi: the VSI being configured
|
|
|
|
* @basename: name for the vector
|
|
|
|
*/
|
|
|
|
static int ice_vsi_req_irq_msix(struct ice_vsi *vsi, char *basename)
|
|
|
|
{
|
|
|
|
int q_vectors = vsi->num_q_vectors;
|
|
|
|
struct ice_pf *pf = vsi->back;
|
ice: Refactor interrupt tracking
Currently we have two MSI-x (IRQ) trackers, one for OS requested MSI-x
entries (sw_irq_tracker) and one for hardware MSI-x vectors
(hw_irq_tracker). Generally the sw_irq_tracker has less entries than the
hw_irq_tracker because the hw_irq_tracker has entries equal to the max
allowed MSI-x per PF and the sw_irq_tracker is mainly the minimum (non
SR-IOV portion of the vectors, kernel granted IRQs). All of the non
SR-IOV portions of the driver (i.e. LAN queues, RDMA queues, OICR, etc.)
take at least one of each type of tracker resource. SR-IOV only grabs
entries from the hw_irq_tracker. There are a few issues with this approach
that can be seen when doing any kind of device reconfiguration (i.e.
ethtool -L, SR-IOV, etc.). One of them being, any time the driver creates
an ice_q_vector and associates it to a LAN queue pair it will grab and
use one entry from the hw_irq_tracker and one from the sw_irq_tracker.
If the indices on these does not match it will cause a Tx timeout, which
will cause a reset and then the indices will match up again and traffic
will resume. The mismatched indices come from the trackers not being the
same size and/or the search_hint in the two trackers not being equal.
Another reason for the refactor is the co-existence of features with
SR-IOV. If SR-IOV is enabled and the interrupts are taken from the end
of the sw_irq_tracker then other features can no longer use this space
because the hardware has now given the remaining interrupts to SR-IOV.
This patch reworks how we track MSI-x vectors by removing the
hw_irq_tracker completely and instead MSI-x resources needed for SR-IOV
are determined all at once instead of per VF. This can be done because
when creating VFs we know how many are wanted and how many MSI-x vectors
each VF needs. This also allows us to start using MSI-x resources from
the end of the PF's allowed MSI-x vectors so we are less likely to use
entries needed for other features (i.e. RDMA, L2 Offload, etc).
This patch also reworks the ice_res_tracker structure by removing the
search_hint and adding a new member - "end". Instead of having a
search_hint we will always search from 0. The new member, "end", will be
used to manipulate the end of the ice_res_tracker (specifically
sw_irq_tracker) during runtime based on MSI-x vectors needed by SR-IOV.
In the normal case, the end of ice_res_tracker will be equal to the
ice_res_tracker's num_entries.
The sriov_base_vector member was added to the PF structure. It is used
to represent the starting MSI-x index of all the needed MSI-x vectors
for all SR-IOV VFs. Depending on how many MSI-x are needed, SR-IOV may
have to take resources from the sw_irq_tracker. This is done by setting
the sw_irq_tracker->end equal to the pf->sriov_base_vector. When all
SR-IOV VFs are removed then the sw_irq_tracker->end is reset back to
sw_irq_tracker->num_entries. The sriov_base_vector, along with the VF's
number of MSI-x (pf->num_vf_msix), vf_id, and the base MSI-x index on
the PF (pf->hw.func_caps.common_cap.msix_vector_first_id), is used to
calculate the first HW absolute MSI-x index for each VF, which is used
to write to the VPINT_ALLOC[_PCI] and GLINT_VECT2FUNC registers to
program the VFs MSI-x PCI configuration bits. Also, the sriov_base_vector
is used along with VF's num_vf_msix, vf_id, and q_vector->v_idx to
determine the MSI-x register index (used for writing to GLINT_DYN_CTL)
within the PF's space.
Interrupt changes removed any references to hw_base_vector, hw_oicr_idx,
and hw_irq_tracker. Only sw_base_vector, sw_oicr_idx, and sw_irq_tracker
variables remain. Change all of these by removing the "sw_" prefix to
help avoid confusion with these variables and their use.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2019-04-16 10:30:44 -07:00
|
|
|
int base = vsi->base_vector;
|
2018-03-20 07:58:13 -07:00
|
|
|
int rx_int_idx = 0;
|
|
|
|
int tx_int_idx = 0;
|
|
|
|
int vector, err;
|
|
|
|
int irq_num;
|
|
|
|
|
|
|
|
for (vector = 0; vector < q_vectors; vector++) {
|
|
|
|
struct ice_q_vector *q_vector = vsi->q_vectors[vector];
|
|
|
|
|
|
|
|
irq_num = pf->msix_entries[base + vector].vector;
|
|
|
|
|
|
|
|
if (q_vector->tx.ring && q_vector->rx.ring) {
|
|
|
|
snprintf(q_vector->name, sizeof(q_vector->name) - 1,
|
|
|
|
"%s-%s-%d", basename, "TxRx", rx_int_idx++);
|
|
|
|
tx_int_idx++;
|
|
|
|
} else if (q_vector->rx.ring) {
|
|
|
|
snprintf(q_vector->name, sizeof(q_vector->name) - 1,
|
|
|
|
"%s-%s-%d", basename, "rx", rx_int_idx++);
|
|
|
|
} else if (q_vector->tx.ring) {
|
|
|
|
snprintf(q_vector->name, sizeof(q_vector->name) - 1,
|
|
|
|
"%s-%s-%d", basename, "tx", tx_int_idx++);
|
|
|
|
} else {
|
|
|
|
/* skip this unused q_vector */
|
|
|
|
continue;
|
|
|
|
}
|
2019-02-26 16:35:22 -08:00
|
|
|
err = devm_request_irq(&pf->pdev->dev, irq_num,
|
|
|
|
vsi->irq_handler, 0,
|
|
|
|
q_vector->name, q_vector);
|
2018-03-20 07:58:13 -07:00
|
|
|
if (err) {
|
|
|
|
netdev_err(vsi->netdev,
|
|
|
|
"MSIX request_irq failed, error: %d\n", err);
|
|
|
|
goto free_q_irqs;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* register for affinity change notifications */
|
|
|
|
q_vector->affinity_notify.notify = ice_irq_affinity_notify;
|
|
|
|
q_vector->affinity_notify.release = ice_irq_affinity_release;
|
|
|
|
irq_set_affinity_notifier(irq_num, &q_vector->affinity_notify);
|
|
|
|
|
|
|
|
/* assign the mask for this irq */
|
|
|
|
irq_set_affinity_hint(irq_num, &q_vector->affinity_mask);
|
|
|
|
}
|
|
|
|
|
|
|
|
vsi->irqs_ready = true;
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
free_q_irqs:
|
|
|
|
while (vector) {
|
|
|
|
vector--;
|
|
|
|
irq_num = pf->msix_entries[base + vector].vector,
|
|
|
|
irq_set_affinity_notifier(irq_num, NULL);
|
|
|
|
irq_set_affinity_hint(irq_num, NULL);
|
|
|
|
devm_free_irq(&pf->pdev->dev, irq_num, &vsi->q_vectors[vector]);
|
|
|
|
}
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
/**
|
|
|
|
* ice_ena_misc_vector - enable the non-queue interrupts
|
|
|
|
* @pf: board private structure
|
|
|
|
*/
|
|
|
|
static void ice_ena_misc_vector(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
u32 val;
|
|
|
|
|
|
|
|
/* clear things first */
|
|
|
|
wr32(hw, PFINT_OICR_ENA, 0); /* disable all */
|
|
|
|
rd32(hw, PFINT_OICR); /* read to clear */
|
|
|
|
|
2018-08-09 06:28:59 -07:00
|
|
|
val = (PFINT_OICR_ECC_ERR_M |
|
2018-03-20 07:58:10 -07:00
|
|
|
PFINT_OICR_MAL_DETECT_M |
|
|
|
|
PFINT_OICR_GRST_M |
|
|
|
|
PFINT_OICR_PCI_EXCEPTION_M |
|
2018-09-19 17:42:57 -07:00
|
|
|
PFINT_OICR_VFLR_M |
|
2018-08-09 06:28:59 -07:00
|
|
|
PFINT_OICR_HMC_ERR_M |
|
|
|
|
PFINT_OICR_PE_CRITERR_M);
|
2018-03-20 07:58:10 -07:00
|
|
|
|
|
|
|
wr32(hw, PFINT_OICR_ENA, val);
|
|
|
|
|
|
|
|
/* SW_ITR_IDX = 0, but don't change INTENA */
|
ice: Refactor interrupt tracking
Currently we have two MSI-x (IRQ) trackers, one for OS requested MSI-x
entries (sw_irq_tracker) and one for hardware MSI-x vectors
(hw_irq_tracker). Generally the sw_irq_tracker has less entries than the
hw_irq_tracker because the hw_irq_tracker has entries equal to the max
allowed MSI-x per PF and the sw_irq_tracker is mainly the minimum (non
SR-IOV portion of the vectors, kernel granted IRQs). All of the non
SR-IOV portions of the driver (i.e. LAN queues, RDMA queues, OICR, etc.)
take at least one of each type of tracker resource. SR-IOV only grabs
entries from the hw_irq_tracker. There are a few issues with this approach
that can be seen when doing any kind of device reconfiguration (i.e.
ethtool -L, SR-IOV, etc.). One of them being, any time the driver creates
an ice_q_vector and associates it to a LAN queue pair it will grab and
use one entry from the hw_irq_tracker and one from the sw_irq_tracker.
If the indices on these does not match it will cause a Tx timeout, which
will cause a reset and then the indices will match up again and traffic
will resume. The mismatched indices come from the trackers not being the
same size and/or the search_hint in the two trackers not being equal.
Another reason for the refactor is the co-existence of features with
SR-IOV. If SR-IOV is enabled and the interrupts are taken from the end
of the sw_irq_tracker then other features can no longer use this space
because the hardware has now given the remaining interrupts to SR-IOV.
This patch reworks how we track MSI-x vectors by removing the
hw_irq_tracker completely and instead MSI-x resources needed for SR-IOV
are determined all at once instead of per VF. This can be done because
when creating VFs we know how many are wanted and how many MSI-x vectors
each VF needs. This also allows us to start using MSI-x resources from
the end of the PF's allowed MSI-x vectors so we are less likely to use
entries needed for other features (i.e. RDMA, L2 Offload, etc).
This patch also reworks the ice_res_tracker structure by removing the
search_hint and adding a new member - "end". Instead of having a
search_hint we will always search from 0. The new member, "end", will be
used to manipulate the end of the ice_res_tracker (specifically
sw_irq_tracker) during runtime based on MSI-x vectors needed by SR-IOV.
In the normal case, the end of ice_res_tracker will be equal to the
ice_res_tracker's num_entries.
The sriov_base_vector member was added to the PF structure. It is used
to represent the starting MSI-x index of all the needed MSI-x vectors
for all SR-IOV VFs. Depending on how many MSI-x are needed, SR-IOV may
have to take resources from the sw_irq_tracker. This is done by setting
the sw_irq_tracker->end equal to the pf->sriov_base_vector. When all
SR-IOV VFs are removed then the sw_irq_tracker->end is reset back to
sw_irq_tracker->num_entries. The sriov_base_vector, along with the VF's
number of MSI-x (pf->num_vf_msix), vf_id, and the base MSI-x index on
the PF (pf->hw.func_caps.common_cap.msix_vector_first_id), is used to
calculate the first HW absolute MSI-x index for each VF, which is used
to write to the VPINT_ALLOC[_PCI] and GLINT_VECT2FUNC registers to
program the VFs MSI-x PCI configuration bits. Also, the sriov_base_vector
is used along with VF's num_vf_msix, vf_id, and q_vector->v_idx to
determine the MSI-x register index (used for writing to GLINT_DYN_CTL)
within the PF's space.
Interrupt changes removed any references to hw_base_vector, hw_oicr_idx,
and hw_irq_tracker. Only sw_base_vector, sw_oicr_idx, and sw_irq_tracker
variables remain. Change all of these by removing the "sw_" prefix to
help avoid confusion with these variables and their use.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2019-04-16 10:30:44 -07:00
|
|
|
wr32(hw, GLINT_DYN_CTL(pf->oicr_idx),
|
2018-03-20 07:58:10 -07:00
|
|
|
GLINT_DYN_CTL_SW_ITR_INDX_M | GLINT_DYN_CTL_INTENA_MSK_M);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_misc_intr - misc interrupt handler
|
|
|
|
* @irq: interrupt number
|
|
|
|
* @data: pointer to a q_vector
|
|
|
|
*/
|
|
|
|
static irqreturn_t ice_misc_intr(int __always_unused irq, void *data)
|
|
|
|
{
|
|
|
|
struct ice_pf *pf = (struct ice_pf *)data;
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
irqreturn_t ret = IRQ_NONE;
|
|
|
|
u32 oicr, ena_mask;
|
|
|
|
|
|
|
|
set_bit(__ICE_ADMINQ_EVENT_PENDING, pf->state);
|
2018-09-19 17:42:54 -07:00
|
|
|
set_bit(__ICE_MAILBOXQ_EVENT_PENDING, pf->state);
|
2018-03-20 07:58:10 -07:00
|
|
|
|
|
|
|
oicr = rd32(hw, PFINT_OICR);
|
|
|
|
ena_mask = rd32(hw, PFINT_OICR_ENA);
|
|
|
|
|
2019-04-16 10:30:43 -07:00
|
|
|
if (oicr & PFINT_OICR_SWINT_M) {
|
|
|
|
ena_mask &= ~PFINT_OICR_SWINT_M;
|
|
|
|
pf->sw_int_count++;
|
|
|
|
}
|
|
|
|
|
2018-08-09 06:29:53 -07:00
|
|
|
if (oicr & PFINT_OICR_MAL_DETECT_M) {
|
|
|
|
ena_mask &= ~PFINT_OICR_MAL_DETECT_M;
|
|
|
|
set_bit(__ICE_MDD_EVENT_PENDING, pf->state);
|
|
|
|
}
|
2018-09-19 17:42:57 -07:00
|
|
|
if (oicr & PFINT_OICR_VFLR_M) {
|
|
|
|
ena_mask &= ~PFINT_OICR_VFLR_M;
|
|
|
|
set_bit(__ICE_VFLR_EVENT_PENDING, pf->state);
|
|
|
|
}
|
2018-08-09 06:29:53 -07:00
|
|
|
|
2018-03-20 07:58:18 -07:00
|
|
|
if (oicr & PFINT_OICR_GRST_M) {
|
|
|
|
u32 reset;
|
2018-08-09 06:29:53 -07:00
|
|
|
|
2018-03-20 07:58:18 -07:00
|
|
|
/* we have a reset warning */
|
|
|
|
ena_mask &= ~PFINT_OICR_GRST_M;
|
|
|
|
reset = (rd32(hw, GLGEN_RSTAT) & GLGEN_RSTAT_RESET_TYPE_M) >>
|
|
|
|
GLGEN_RSTAT_RESET_TYPE_S;
|
|
|
|
|
|
|
|
if (reset == ICE_RESET_CORER)
|
|
|
|
pf->corer_count++;
|
|
|
|
else if (reset == ICE_RESET_GLOBR)
|
|
|
|
pf->globr_count++;
|
2018-09-19 17:23:18 -07:00
|
|
|
else if (reset == ICE_RESET_EMPR)
|
2018-03-20 07:58:18 -07:00
|
|
|
pf->empr_count++;
|
2018-09-19 17:23:18 -07:00
|
|
|
else
|
|
|
|
dev_dbg(&pf->pdev->dev, "Invalid reset type %d\n",
|
|
|
|
reset);
|
2018-03-20 07:58:18 -07:00
|
|
|
|
|
|
|
/* If a reset cycle isn't already in progress, we set a bit in
|
|
|
|
* pf->state so that the service task can start a reset/rebuild.
|
|
|
|
* We also make note of which reset happened so that peer
|
|
|
|
* devices/drivers can be informed.
|
|
|
|
*/
|
2018-09-19 17:23:11 -07:00
|
|
|
if (!test_and_set_bit(__ICE_RESET_OICR_RECV, pf->state)) {
|
2018-03-20 07:58:18 -07:00
|
|
|
if (reset == ICE_RESET_CORER)
|
|
|
|
set_bit(__ICE_CORER_RECV, pf->state);
|
|
|
|
else if (reset == ICE_RESET_GLOBR)
|
|
|
|
set_bit(__ICE_GLOBR_RECV, pf->state);
|
|
|
|
else
|
|
|
|
set_bit(__ICE_EMPR_RECV, pf->state);
|
|
|
|
|
2018-08-09 06:29:47 -07:00
|
|
|
/* There are couple of different bits at play here.
|
|
|
|
* hw->reset_ongoing indicates whether the hardware is
|
|
|
|
* in reset. This is set to true when a reset interrupt
|
|
|
|
* is received and set back to false after the driver
|
|
|
|
* has determined that the hardware is out of reset.
|
|
|
|
*
|
2018-09-19 17:23:11 -07:00
|
|
|
* __ICE_RESET_OICR_RECV in pf->state indicates
|
2018-08-09 06:29:47 -07:00
|
|
|
* that a post reset rebuild is required before the
|
|
|
|
* driver is operational again. This is set above.
|
|
|
|
*
|
|
|
|
* As this is the start of the reset/rebuild cycle, set
|
|
|
|
* both to indicate that.
|
|
|
|
*/
|
|
|
|
hw->reset_ongoing = true;
|
2018-03-20 07:58:18 -07:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
if (oicr & PFINT_OICR_HMC_ERR_M) {
|
|
|
|
ena_mask &= ~PFINT_OICR_HMC_ERR_M;
|
|
|
|
dev_dbg(&pf->pdev->dev,
|
|
|
|
"HMC Error interrupt - info 0x%x, data 0x%x\n",
|
|
|
|
rd32(hw, PFHMC_ERRORINFO),
|
|
|
|
rd32(hw, PFHMC_ERRORDATA));
|
|
|
|
}
|
|
|
|
|
2019-02-28 15:25:58 -08:00
|
|
|
/* Report any remaining unexpected interrupts */
|
2018-03-20 07:58:10 -07:00
|
|
|
oicr &= ena_mask;
|
|
|
|
if (oicr) {
|
|
|
|
dev_dbg(&pf->pdev->dev, "unhandled interrupt oicr=0x%08x\n",
|
|
|
|
oicr);
|
|
|
|
/* If a critical error is pending there is no choice but to
|
|
|
|
* reset the device.
|
|
|
|
*/
|
|
|
|
if (oicr & (PFINT_OICR_PE_CRITERR_M |
|
|
|
|
PFINT_OICR_PCI_EXCEPTION_M |
|
2018-03-20 07:58:18 -07:00
|
|
|
PFINT_OICR_ECC_ERR_M)) {
|
2018-03-20 07:58:10 -07:00
|
|
|
set_bit(__ICE_PFR_REQ, pf->state);
|
2018-03-20 07:58:18 -07:00
|
|
|
ice_service_task_schedule(pf);
|
|
|
|
}
|
2018-03-20 07:58:10 -07:00
|
|
|
}
|
|
|
|
ret = IRQ_HANDLED;
|
|
|
|
|
|
|
|
if (!test_bit(__ICE_DOWN, pf->state)) {
|
|
|
|
ice_service_task_schedule(pf);
|
2018-03-20 07:58:13 -07:00
|
|
|
ice_irq_dynamic_ena(hw, NULL, NULL);
|
2018-03-20 07:58:10 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2019-02-08 12:50:34 -08:00
|
|
|
/**
|
|
|
|
* ice_dis_ctrlq_interrupts - disable control queue interrupts
|
|
|
|
* @hw: pointer to HW structure
|
|
|
|
*/
|
|
|
|
static void ice_dis_ctrlq_interrupts(struct ice_hw *hw)
|
|
|
|
{
|
|
|
|
/* disable Admin queue Interrupt causes */
|
|
|
|
wr32(hw, PFINT_FW_CTL,
|
|
|
|
rd32(hw, PFINT_FW_CTL) & ~PFINT_FW_CTL_CAUSE_ENA_M);
|
|
|
|
|
|
|
|
/* disable Mailbox queue Interrupt causes */
|
|
|
|
wr32(hw, PFINT_MBX_CTL,
|
|
|
|
rd32(hw, PFINT_MBX_CTL) & ~PFINT_MBX_CTL_CAUSE_ENA_M);
|
|
|
|
|
|
|
|
/* disable Control queue Interrupt causes */
|
|
|
|
wr32(hw, PFINT_OICR_CTL,
|
|
|
|
rd32(hw, PFINT_OICR_CTL) & ~PFINT_OICR_CTL_CAUSE_ENA_M);
|
|
|
|
|
|
|
|
ice_flush(hw);
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
/**
|
|
|
|
* ice_free_irq_msix_misc - Unroll misc vector setup
|
|
|
|
* @pf: board private structure
|
|
|
|
*/
|
|
|
|
static void ice_free_irq_msix_misc(struct ice_pf *pf)
|
|
|
|
{
|
2019-02-08 12:50:34 -08:00
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
|
|
|
|
ice_dis_ctrlq_interrupts(hw);
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
/* disable OICR interrupt */
|
2019-02-08 12:50:34 -08:00
|
|
|
wr32(hw, PFINT_OICR_ENA, 0);
|
|
|
|
ice_flush(hw);
|
2018-03-20 07:58:10 -07:00
|
|
|
|
|
|
|
if (test_bit(ICE_FLAG_MSIX_ENA, pf->flags) && pf->msix_entries) {
|
ice: Refactor interrupt tracking
Currently we have two MSI-x (IRQ) trackers, one for OS requested MSI-x
entries (sw_irq_tracker) and one for hardware MSI-x vectors
(hw_irq_tracker). Generally the sw_irq_tracker has less entries than the
hw_irq_tracker because the hw_irq_tracker has entries equal to the max
allowed MSI-x per PF and the sw_irq_tracker is mainly the minimum (non
SR-IOV portion of the vectors, kernel granted IRQs). All of the non
SR-IOV portions of the driver (i.e. LAN queues, RDMA queues, OICR, etc.)
take at least one of each type of tracker resource. SR-IOV only grabs
entries from the hw_irq_tracker. There are a few issues with this approach
that can be seen when doing any kind of device reconfiguration (i.e.
ethtool -L, SR-IOV, etc.). One of them being, any time the driver creates
an ice_q_vector and associates it to a LAN queue pair it will grab and
use one entry from the hw_irq_tracker and one from the sw_irq_tracker.
If the indices on these does not match it will cause a Tx timeout, which
will cause a reset and then the indices will match up again and traffic
will resume. The mismatched indices come from the trackers not being the
same size and/or the search_hint in the two trackers not being equal.
Another reason for the refactor is the co-existence of features with
SR-IOV. If SR-IOV is enabled and the interrupts are taken from the end
of the sw_irq_tracker then other features can no longer use this space
because the hardware has now given the remaining interrupts to SR-IOV.
This patch reworks how we track MSI-x vectors by removing the
hw_irq_tracker completely and instead MSI-x resources needed for SR-IOV
are determined all at once instead of per VF. This can be done because
when creating VFs we know how many are wanted and how many MSI-x vectors
each VF needs. This also allows us to start using MSI-x resources from
the end of the PF's allowed MSI-x vectors so we are less likely to use
entries needed for other features (i.e. RDMA, L2 Offload, etc).
This patch also reworks the ice_res_tracker structure by removing the
search_hint and adding a new member - "end". Instead of having a
search_hint we will always search from 0. The new member, "end", will be
used to manipulate the end of the ice_res_tracker (specifically
sw_irq_tracker) during runtime based on MSI-x vectors needed by SR-IOV.
In the normal case, the end of ice_res_tracker will be equal to the
ice_res_tracker's num_entries.
The sriov_base_vector member was added to the PF structure. It is used
to represent the starting MSI-x index of all the needed MSI-x vectors
for all SR-IOV VFs. Depending on how many MSI-x are needed, SR-IOV may
have to take resources from the sw_irq_tracker. This is done by setting
the sw_irq_tracker->end equal to the pf->sriov_base_vector. When all
SR-IOV VFs are removed then the sw_irq_tracker->end is reset back to
sw_irq_tracker->num_entries. The sriov_base_vector, along with the VF's
number of MSI-x (pf->num_vf_msix), vf_id, and the base MSI-x index on
the PF (pf->hw.func_caps.common_cap.msix_vector_first_id), is used to
calculate the first HW absolute MSI-x index for each VF, which is used
to write to the VPINT_ALLOC[_PCI] and GLINT_VECT2FUNC registers to
program the VFs MSI-x PCI configuration bits. Also, the sriov_base_vector
is used along with VF's num_vf_msix, vf_id, and q_vector->v_idx to
determine the MSI-x register index (used for writing to GLINT_DYN_CTL)
within the PF's space.
Interrupt changes removed any references to hw_base_vector, hw_oicr_idx,
and hw_irq_tracker. Only sw_base_vector, sw_oicr_idx, and sw_irq_tracker
variables remain. Change all of these by removing the "sw_" prefix to
help avoid confusion with these variables and their use.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2019-04-16 10:30:44 -07:00
|
|
|
synchronize_irq(pf->msix_entries[pf->oicr_idx].vector);
|
2018-03-20 07:58:10 -07:00
|
|
|
devm_free_irq(&pf->pdev->dev,
|
ice: Refactor interrupt tracking
Currently we have two MSI-x (IRQ) trackers, one for OS requested MSI-x
entries (sw_irq_tracker) and one for hardware MSI-x vectors
(hw_irq_tracker). Generally the sw_irq_tracker has less entries than the
hw_irq_tracker because the hw_irq_tracker has entries equal to the max
allowed MSI-x per PF and the sw_irq_tracker is mainly the minimum (non
SR-IOV portion of the vectors, kernel granted IRQs). All of the non
SR-IOV portions of the driver (i.e. LAN queues, RDMA queues, OICR, etc.)
take at least one of each type of tracker resource. SR-IOV only grabs
entries from the hw_irq_tracker. There are a few issues with this approach
that can be seen when doing any kind of device reconfiguration (i.e.
ethtool -L, SR-IOV, etc.). One of them being, any time the driver creates
an ice_q_vector and associates it to a LAN queue pair it will grab and
use one entry from the hw_irq_tracker and one from the sw_irq_tracker.
If the indices on these does not match it will cause a Tx timeout, which
will cause a reset and then the indices will match up again and traffic
will resume. The mismatched indices come from the trackers not being the
same size and/or the search_hint in the two trackers not being equal.
Another reason for the refactor is the co-existence of features with
SR-IOV. If SR-IOV is enabled and the interrupts are taken from the end
of the sw_irq_tracker then other features can no longer use this space
because the hardware has now given the remaining interrupts to SR-IOV.
This patch reworks how we track MSI-x vectors by removing the
hw_irq_tracker completely and instead MSI-x resources needed for SR-IOV
are determined all at once instead of per VF. This can be done because
when creating VFs we know how many are wanted and how many MSI-x vectors
each VF needs. This also allows us to start using MSI-x resources from
the end of the PF's allowed MSI-x vectors so we are less likely to use
entries needed for other features (i.e. RDMA, L2 Offload, etc).
This patch also reworks the ice_res_tracker structure by removing the
search_hint and adding a new member - "end". Instead of having a
search_hint we will always search from 0. The new member, "end", will be
used to manipulate the end of the ice_res_tracker (specifically
sw_irq_tracker) during runtime based on MSI-x vectors needed by SR-IOV.
In the normal case, the end of ice_res_tracker will be equal to the
ice_res_tracker's num_entries.
The sriov_base_vector member was added to the PF structure. It is used
to represent the starting MSI-x index of all the needed MSI-x vectors
for all SR-IOV VFs. Depending on how many MSI-x are needed, SR-IOV may
have to take resources from the sw_irq_tracker. This is done by setting
the sw_irq_tracker->end equal to the pf->sriov_base_vector. When all
SR-IOV VFs are removed then the sw_irq_tracker->end is reset back to
sw_irq_tracker->num_entries. The sriov_base_vector, along with the VF's
number of MSI-x (pf->num_vf_msix), vf_id, and the base MSI-x index on
the PF (pf->hw.func_caps.common_cap.msix_vector_first_id), is used to
calculate the first HW absolute MSI-x index for each VF, which is used
to write to the VPINT_ALLOC[_PCI] and GLINT_VECT2FUNC registers to
program the VFs MSI-x PCI configuration bits. Also, the sriov_base_vector
is used along with VF's num_vf_msix, vf_id, and q_vector->v_idx to
determine the MSI-x register index (used for writing to GLINT_DYN_CTL)
within the PF's space.
Interrupt changes removed any references to hw_base_vector, hw_oicr_idx,
and hw_irq_tracker. Only sw_base_vector, sw_oicr_idx, and sw_irq_tracker
variables remain. Change all of these by removing the "sw_" prefix to
help avoid confusion with these variables and their use.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2019-04-16 10:30:44 -07:00
|
|
|
pf->msix_entries[pf->oicr_idx].vector, pf);
|
2018-03-20 07:58:10 -07:00
|
|
|
}
|
|
|
|
|
ice: Split irq_tracker into sw_irq_tracker and hw_irq_tracker
For the PF driver, when mapping interrupts to queues, we need to request
IRQs from the kernel and we also have to allocate interrupts from
the device.
Similarly, when the VF driver (iavf.ko) initializes, it requests the kernel
IRQs that it needs but it can't directly allocate interrupts in the device.
Instead, it sends a mailbox message to the ice driver, which then allocates
interrupts in the device on the VF driver's behalf.
Currently both these cases end up having to reserve entries in
pf->irq_tracker but irq_tracker itself is sized based on how many vectors
the PF driver needs. Under the right circumstances, the VF driver can fail
to get entries in irq_tracker, which will result in the VF driver failing
probe.
To fix this, sw_irq_tracker and hw_irq_tracker are introduced. The
sw_irq_tracker tracks only the PF's IRQ request and doesn't play any
role in VF init. hw_irq_tracker represents the device's interrupt space.
When interrupts have to be allocated in the device for either PF or VF,
hw_irq_tracker will be looked up to see if the device has run out of
interrupts.
Signed-off-by: Preethi Banala <preethi.banala@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-09-19 17:23:16 -07:00
|
|
|
pf->num_avail_sw_msix += 1;
|
ice: Refactor interrupt tracking
Currently we have two MSI-x (IRQ) trackers, one for OS requested MSI-x
entries (sw_irq_tracker) and one for hardware MSI-x vectors
(hw_irq_tracker). Generally the sw_irq_tracker has less entries than the
hw_irq_tracker because the hw_irq_tracker has entries equal to the max
allowed MSI-x per PF and the sw_irq_tracker is mainly the minimum (non
SR-IOV portion of the vectors, kernel granted IRQs). All of the non
SR-IOV portions of the driver (i.e. LAN queues, RDMA queues, OICR, etc.)
take at least one of each type of tracker resource. SR-IOV only grabs
entries from the hw_irq_tracker. There are a few issues with this approach
that can be seen when doing any kind of device reconfiguration (i.e.
ethtool -L, SR-IOV, etc.). One of them being, any time the driver creates
an ice_q_vector and associates it to a LAN queue pair it will grab and
use one entry from the hw_irq_tracker and one from the sw_irq_tracker.
If the indices on these does not match it will cause a Tx timeout, which
will cause a reset and then the indices will match up again and traffic
will resume. The mismatched indices come from the trackers not being the
same size and/or the search_hint in the two trackers not being equal.
Another reason for the refactor is the co-existence of features with
SR-IOV. If SR-IOV is enabled and the interrupts are taken from the end
of the sw_irq_tracker then other features can no longer use this space
because the hardware has now given the remaining interrupts to SR-IOV.
This patch reworks how we track MSI-x vectors by removing the
hw_irq_tracker completely and instead MSI-x resources needed for SR-IOV
are determined all at once instead of per VF. This can be done because
when creating VFs we know how many are wanted and how many MSI-x vectors
each VF needs. This also allows us to start using MSI-x resources from
the end of the PF's allowed MSI-x vectors so we are less likely to use
entries needed for other features (i.e. RDMA, L2 Offload, etc).
This patch also reworks the ice_res_tracker structure by removing the
search_hint and adding a new member - "end". Instead of having a
search_hint we will always search from 0. The new member, "end", will be
used to manipulate the end of the ice_res_tracker (specifically
sw_irq_tracker) during runtime based on MSI-x vectors needed by SR-IOV.
In the normal case, the end of ice_res_tracker will be equal to the
ice_res_tracker's num_entries.
The sriov_base_vector member was added to the PF structure. It is used
to represent the starting MSI-x index of all the needed MSI-x vectors
for all SR-IOV VFs. Depending on how many MSI-x are needed, SR-IOV may
have to take resources from the sw_irq_tracker. This is done by setting
the sw_irq_tracker->end equal to the pf->sriov_base_vector. When all
SR-IOV VFs are removed then the sw_irq_tracker->end is reset back to
sw_irq_tracker->num_entries. The sriov_base_vector, along with the VF's
number of MSI-x (pf->num_vf_msix), vf_id, and the base MSI-x index on
the PF (pf->hw.func_caps.common_cap.msix_vector_first_id), is used to
calculate the first HW absolute MSI-x index for each VF, which is used
to write to the VPINT_ALLOC[_PCI] and GLINT_VECT2FUNC registers to
program the VFs MSI-x PCI configuration bits. Also, the sriov_base_vector
is used along with VF's num_vf_msix, vf_id, and q_vector->v_idx to
determine the MSI-x register index (used for writing to GLINT_DYN_CTL)
within the PF's space.
Interrupt changes removed any references to hw_base_vector, hw_oicr_idx,
and hw_irq_tracker. Only sw_base_vector, sw_oicr_idx, and sw_irq_tracker
variables remain. Change all of these by removing the "sw_" prefix to
help avoid confusion with these variables and their use.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2019-04-16 10:30:44 -07:00
|
|
|
ice_free_res(pf->irq_tracker, pf->oicr_idx, ICE_RES_MISC_VEC_ID);
|
2018-03-20 07:58:10 -07:00
|
|
|
}
|
|
|
|
|
2019-02-08 12:50:34 -08:00
|
|
|
/**
|
|
|
|
* ice_ena_ctrlq_interrupts - enable control queue interrupts
|
|
|
|
* @hw: pointer to HW structure
|
2019-02-28 15:25:59 -08:00
|
|
|
* @reg_idx: HW vector index to associate the control queue interrupts with
|
2019-02-08 12:50:34 -08:00
|
|
|
*/
|
2019-02-28 15:25:59 -08:00
|
|
|
static void ice_ena_ctrlq_interrupts(struct ice_hw *hw, u16 reg_idx)
|
2019-02-08 12:50:34 -08:00
|
|
|
{
|
|
|
|
u32 val;
|
|
|
|
|
2019-02-28 15:25:59 -08:00
|
|
|
val = ((reg_idx & PFINT_OICR_CTL_MSIX_INDX_M) |
|
2019-02-08 12:50:34 -08:00
|
|
|
PFINT_OICR_CTL_CAUSE_ENA_M);
|
|
|
|
wr32(hw, PFINT_OICR_CTL, val);
|
|
|
|
|
|
|
|
/* enable Admin queue Interrupt causes */
|
2019-02-28 15:25:59 -08:00
|
|
|
val = ((reg_idx & PFINT_FW_CTL_MSIX_INDX_M) |
|
2019-02-08 12:50:34 -08:00
|
|
|
PFINT_FW_CTL_CAUSE_ENA_M);
|
|
|
|
wr32(hw, PFINT_FW_CTL, val);
|
|
|
|
|
|
|
|
/* enable Mailbox queue Interrupt causes */
|
2019-02-28 15:25:59 -08:00
|
|
|
val = ((reg_idx & PFINT_MBX_CTL_MSIX_INDX_M) |
|
2019-02-08 12:50:34 -08:00
|
|
|
PFINT_MBX_CTL_CAUSE_ENA_M);
|
|
|
|
wr32(hw, PFINT_MBX_CTL, val);
|
|
|
|
|
|
|
|
ice_flush(hw);
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
/**
|
|
|
|
* ice_req_irq_msix_misc - Setup the misc vector to handle non queue events
|
|
|
|
* @pf: board private structure
|
|
|
|
*
|
|
|
|
* This sets up the handler for MSIX 0, which is used to manage the
|
2018-10-26 11:44:46 -07:00
|
|
|
* non-queue interrupts, e.g. AdminQ and errors. This is not used
|
2018-03-20 07:58:10 -07:00
|
|
|
* when in MSI or Legacy interrupt mode.
|
|
|
|
*/
|
|
|
|
static int ice_req_irq_msix_misc(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
int oicr_idx, err = 0;
|
|
|
|
|
|
|
|
if (!pf->int_name[0])
|
|
|
|
snprintf(pf->int_name, sizeof(pf->int_name) - 1, "%s-%s:misc",
|
|
|
|
dev_driver_string(&pf->pdev->dev),
|
|
|
|
dev_name(&pf->pdev->dev));
|
|
|
|
|
2018-03-20 07:58:18 -07:00
|
|
|
/* Do not request IRQ but do enable OICR interrupt since settings are
|
|
|
|
* lost during reset. Note that this function is called only during
|
|
|
|
* rebuild path and not while reset is in progress.
|
|
|
|
*/
|
2018-09-19 17:23:11 -07:00
|
|
|
if (ice_is_reset_in_progress(pf->state))
|
2018-03-20 07:58:18 -07:00
|
|
|
goto skip_req_irq;
|
|
|
|
|
ice: Refactor interrupt tracking
Currently we have two MSI-x (IRQ) trackers, one for OS requested MSI-x
entries (sw_irq_tracker) and one for hardware MSI-x vectors
(hw_irq_tracker). Generally the sw_irq_tracker has less entries than the
hw_irq_tracker because the hw_irq_tracker has entries equal to the max
allowed MSI-x per PF and the sw_irq_tracker is mainly the minimum (non
SR-IOV portion of the vectors, kernel granted IRQs). All of the non
SR-IOV portions of the driver (i.e. LAN queues, RDMA queues, OICR, etc.)
take at least one of each type of tracker resource. SR-IOV only grabs
entries from the hw_irq_tracker. There are a few issues with this approach
that can be seen when doing any kind of device reconfiguration (i.e.
ethtool -L, SR-IOV, etc.). One of them being, any time the driver creates
an ice_q_vector and associates it to a LAN queue pair it will grab and
use one entry from the hw_irq_tracker and one from the sw_irq_tracker.
If the indices on these does not match it will cause a Tx timeout, which
will cause a reset and then the indices will match up again and traffic
will resume. The mismatched indices come from the trackers not being the
same size and/or the search_hint in the two trackers not being equal.
Another reason for the refactor is the co-existence of features with
SR-IOV. If SR-IOV is enabled and the interrupts are taken from the end
of the sw_irq_tracker then other features can no longer use this space
because the hardware has now given the remaining interrupts to SR-IOV.
This patch reworks how we track MSI-x vectors by removing the
hw_irq_tracker completely and instead MSI-x resources needed for SR-IOV
are determined all at once instead of per VF. This can be done because
when creating VFs we know how many are wanted and how many MSI-x vectors
each VF needs. This also allows us to start using MSI-x resources from
the end of the PF's allowed MSI-x vectors so we are less likely to use
entries needed for other features (i.e. RDMA, L2 Offload, etc).
This patch also reworks the ice_res_tracker structure by removing the
search_hint and adding a new member - "end". Instead of having a
search_hint we will always search from 0. The new member, "end", will be
used to manipulate the end of the ice_res_tracker (specifically
sw_irq_tracker) during runtime based on MSI-x vectors needed by SR-IOV.
In the normal case, the end of ice_res_tracker will be equal to the
ice_res_tracker's num_entries.
The sriov_base_vector member was added to the PF structure. It is used
to represent the starting MSI-x index of all the needed MSI-x vectors
for all SR-IOV VFs. Depending on how many MSI-x are needed, SR-IOV may
have to take resources from the sw_irq_tracker. This is done by setting
the sw_irq_tracker->end equal to the pf->sriov_base_vector. When all
SR-IOV VFs are removed then the sw_irq_tracker->end is reset back to
sw_irq_tracker->num_entries. The sriov_base_vector, along with the VF's
number of MSI-x (pf->num_vf_msix), vf_id, and the base MSI-x index on
the PF (pf->hw.func_caps.common_cap.msix_vector_first_id), is used to
calculate the first HW absolute MSI-x index for each VF, which is used
to write to the VPINT_ALLOC[_PCI] and GLINT_VECT2FUNC registers to
program the VFs MSI-x PCI configuration bits. Also, the sriov_base_vector
is used along with VF's num_vf_msix, vf_id, and q_vector->v_idx to
determine the MSI-x register index (used for writing to GLINT_DYN_CTL)
within the PF's space.
Interrupt changes removed any references to hw_base_vector, hw_oicr_idx,
and hw_irq_tracker. Only sw_base_vector, sw_oicr_idx, and sw_irq_tracker
variables remain. Change all of these by removing the "sw_" prefix to
help avoid confusion with these variables and their use.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2019-04-16 10:30:44 -07:00
|
|
|
/* reserve one vector in irq_tracker for misc interrupts */
|
|
|
|
oicr_idx = ice_get_res(pf, pf->irq_tracker, 1, ICE_RES_MISC_VEC_ID);
|
2018-03-20 07:58:10 -07:00
|
|
|
if (oicr_idx < 0)
|
|
|
|
return oicr_idx;
|
|
|
|
|
ice: Split irq_tracker into sw_irq_tracker and hw_irq_tracker
For the PF driver, when mapping interrupts to queues, we need to request
IRQs from the kernel and we also have to allocate interrupts from
the device.
Similarly, when the VF driver (iavf.ko) initializes, it requests the kernel
IRQs that it needs but it can't directly allocate interrupts in the device.
Instead, it sends a mailbox message to the ice driver, which then allocates
interrupts in the device on the VF driver's behalf.
Currently both these cases end up having to reserve entries in
pf->irq_tracker but irq_tracker itself is sized based on how many vectors
the PF driver needs. Under the right circumstances, the VF driver can fail
to get entries in irq_tracker, which will result in the VF driver failing
probe.
To fix this, sw_irq_tracker and hw_irq_tracker are introduced. The
sw_irq_tracker tracks only the PF's IRQ request and doesn't play any
role in VF init. hw_irq_tracker represents the device's interrupt space.
When interrupts have to be allocated in the device for either PF or VF,
hw_irq_tracker will be looked up to see if the device has run out of
interrupts.
Signed-off-by: Preethi Banala <preethi.banala@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-09-19 17:23:16 -07:00
|
|
|
pf->num_avail_sw_msix -= 1;
|
ice: Refactor interrupt tracking
Currently we have two MSI-x (IRQ) trackers, one for OS requested MSI-x
entries (sw_irq_tracker) and one for hardware MSI-x vectors
(hw_irq_tracker). Generally the sw_irq_tracker has less entries than the
hw_irq_tracker because the hw_irq_tracker has entries equal to the max
allowed MSI-x per PF and the sw_irq_tracker is mainly the minimum (non
SR-IOV portion of the vectors, kernel granted IRQs). All of the non
SR-IOV portions of the driver (i.e. LAN queues, RDMA queues, OICR, etc.)
take at least one of each type of tracker resource. SR-IOV only grabs
entries from the hw_irq_tracker. There are a few issues with this approach
that can be seen when doing any kind of device reconfiguration (i.e.
ethtool -L, SR-IOV, etc.). One of them being, any time the driver creates
an ice_q_vector and associates it to a LAN queue pair it will grab and
use one entry from the hw_irq_tracker and one from the sw_irq_tracker.
If the indices on these does not match it will cause a Tx timeout, which
will cause a reset and then the indices will match up again and traffic
will resume. The mismatched indices come from the trackers not being the
same size and/or the search_hint in the two trackers not being equal.
Another reason for the refactor is the co-existence of features with
SR-IOV. If SR-IOV is enabled and the interrupts are taken from the end
of the sw_irq_tracker then other features can no longer use this space
because the hardware has now given the remaining interrupts to SR-IOV.
This patch reworks how we track MSI-x vectors by removing the
hw_irq_tracker completely and instead MSI-x resources needed for SR-IOV
are determined all at once instead of per VF. This can be done because
when creating VFs we know how many are wanted and how many MSI-x vectors
each VF needs. This also allows us to start using MSI-x resources from
the end of the PF's allowed MSI-x vectors so we are less likely to use
entries needed for other features (i.e. RDMA, L2 Offload, etc).
This patch also reworks the ice_res_tracker structure by removing the
search_hint and adding a new member - "end". Instead of having a
search_hint we will always search from 0. The new member, "end", will be
used to manipulate the end of the ice_res_tracker (specifically
sw_irq_tracker) during runtime based on MSI-x vectors needed by SR-IOV.
In the normal case, the end of ice_res_tracker will be equal to the
ice_res_tracker's num_entries.
The sriov_base_vector member was added to the PF structure. It is used
to represent the starting MSI-x index of all the needed MSI-x vectors
for all SR-IOV VFs. Depending on how many MSI-x are needed, SR-IOV may
have to take resources from the sw_irq_tracker. This is done by setting
the sw_irq_tracker->end equal to the pf->sriov_base_vector. When all
SR-IOV VFs are removed then the sw_irq_tracker->end is reset back to
sw_irq_tracker->num_entries. The sriov_base_vector, along with the VF's
number of MSI-x (pf->num_vf_msix), vf_id, and the base MSI-x index on
the PF (pf->hw.func_caps.common_cap.msix_vector_first_id), is used to
calculate the first HW absolute MSI-x index for each VF, which is used
to write to the VPINT_ALLOC[_PCI] and GLINT_VECT2FUNC registers to
program the VFs MSI-x PCI configuration bits. Also, the sriov_base_vector
is used along with VF's num_vf_msix, vf_id, and q_vector->v_idx to
determine the MSI-x register index (used for writing to GLINT_DYN_CTL)
within the PF's space.
Interrupt changes removed any references to hw_base_vector, hw_oicr_idx,
and hw_irq_tracker. Only sw_base_vector, sw_oicr_idx, and sw_irq_tracker
variables remain. Change all of these by removing the "sw_" prefix to
help avoid confusion with these variables and their use.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2019-04-16 10:30:44 -07:00
|
|
|
pf->oicr_idx = oicr_idx;
|
2018-03-20 07:58:10 -07:00
|
|
|
|
|
|
|
err = devm_request_irq(&pf->pdev->dev,
|
ice: Refactor interrupt tracking
Currently we have two MSI-x (IRQ) trackers, one for OS requested MSI-x
entries (sw_irq_tracker) and one for hardware MSI-x vectors
(hw_irq_tracker). Generally the sw_irq_tracker has less entries than the
hw_irq_tracker because the hw_irq_tracker has entries equal to the max
allowed MSI-x per PF and the sw_irq_tracker is mainly the minimum (non
SR-IOV portion of the vectors, kernel granted IRQs). All of the non
SR-IOV portions of the driver (i.e. LAN queues, RDMA queues, OICR, etc.)
take at least one of each type of tracker resource. SR-IOV only grabs
entries from the hw_irq_tracker. There are a few issues with this approach
that can be seen when doing any kind of device reconfiguration (i.e.
ethtool -L, SR-IOV, etc.). One of them being, any time the driver creates
an ice_q_vector and associates it to a LAN queue pair it will grab and
use one entry from the hw_irq_tracker and one from the sw_irq_tracker.
If the indices on these does not match it will cause a Tx timeout, which
will cause a reset and then the indices will match up again and traffic
will resume. The mismatched indices come from the trackers not being the
same size and/or the search_hint in the two trackers not being equal.
Another reason for the refactor is the co-existence of features with
SR-IOV. If SR-IOV is enabled and the interrupts are taken from the end
of the sw_irq_tracker then other features can no longer use this space
because the hardware has now given the remaining interrupts to SR-IOV.
This patch reworks how we track MSI-x vectors by removing the
hw_irq_tracker completely and instead MSI-x resources needed for SR-IOV
are determined all at once instead of per VF. This can be done because
when creating VFs we know how many are wanted and how many MSI-x vectors
each VF needs. This also allows us to start using MSI-x resources from
the end of the PF's allowed MSI-x vectors so we are less likely to use
entries needed for other features (i.e. RDMA, L2 Offload, etc).
This patch also reworks the ice_res_tracker structure by removing the
search_hint and adding a new member - "end". Instead of having a
search_hint we will always search from 0. The new member, "end", will be
used to manipulate the end of the ice_res_tracker (specifically
sw_irq_tracker) during runtime based on MSI-x vectors needed by SR-IOV.
In the normal case, the end of ice_res_tracker will be equal to the
ice_res_tracker's num_entries.
The sriov_base_vector member was added to the PF structure. It is used
to represent the starting MSI-x index of all the needed MSI-x vectors
for all SR-IOV VFs. Depending on how many MSI-x are needed, SR-IOV may
have to take resources from the sw_irq_tracker. This is done by setting
the sw_irq_tracker->end equal to the pf->sriov_base_vector. When all
SR-IOV VFs are removed then the sw_irq_tracker->end is reset back to
sw_irq_tracker->num_entries. The sriov_base_vector, along with the VF's
number of MSI-x (pf->num_vf_msix), vf_id, and the base MSI-x index on
the PF (pf->hw.func_caps.common_cap.msix_vector_first_id), is used to
calculate the first HW absolute MSI-x index for each VF, which is used
to write to the VPINT_ALLOC[_PCI] and GLINT_VECT2FUNC registers to
program the VFs MSI-x PCI configuration bits. Also, the sriov_base_vector
is used along with VF's num_vf_msix, vf_id, and q_vector->v_idx to
determine the MSI-x register index (used for writing to GLINT_DYN_CTL)
within the PF's space.
Interrupt changes removed any references to hw_base_vector, hw_oicr_idx,
and hw_irq_tracker. Only sw_base_vector, sw_oicr_idx, and sw_irq_tracker
variables remain. Change all of these by removing the "sw_" prefix to
help avoid confusion with these variables and their use.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2019-04-16 10:30:44 -07:00
|
|
|
pf->msix_entries[pf->oicr_idx].vector,
|
2018-03-20 07:58:10 -07:00
|
|
|
ice_misc_intr, 0, pf->int_name, pf);
|
|
|
|
if (err) {
|
|
|
|
dev_err(&pf->pdev->dev,
|
|
|
|
"devm_request_irq for %s failed: %d\n",
|
|
|
|
pf->int_name, err);
|
ice: Refactor interrupt tracking
Currently we have two MSI-x (IRQ) trackers, one for OS requested MSI-x
entries (sw_irq_tracker) and one for hardware MSI-x vectors
(hw_irq_tracker). Generally the sw_irq_tracker has less entries than the
hw_irq_tracker because the hw_irq_tracker has entries equal to the max
allowed MSI-x per PF and the sw_irq_tracker is mainly the minimum (non
SR-IOV portion of the vectors, kernel granted IRQs). All of the non
SR-IOV portions of the driver (i.e. LAN queues, RDMA queues, OICR, etc.)
take at least one of each type of tracker resource. SR-IOV only grabs
entries from the hw_irq_tracker. There are a few issues with this approach
that can be seen when doing any kind of device reconfiguration (i.e.
ethtool -L, SR-IOV, etc.). One of them being, any time the driver creates
an ice_q_vector and associates it to a LAN queue pair it will grab and
use one entry from the hw_irq_tracker and one from the sw_irq_tracker.
If the indices on these does not match it will cause a Tx timeout, which
will cause a reset and then the indices will match up again and traffic
will resume. The mismatched indices come from the trackers not being the
same size and/or the search_hint in the two trackers not being equal.
Another reason for the refactor is the co-existence of features with
SR-IOV. If SR-IOV is enabled and the interrupts are taken from the end
of the sw_irq_tracker then other features can no longer use this space
because the hardware has now given the remaining interrupts to SR-IOV.
This patch reworks how we track MSI-x vectors by removing the
hw_irq_tracker completely and instead MSI-x resources needed for SR-IOV
are determined all at once instead of per VF. This can be done because
when creating VFs we know how many are wanted and how many MSI-x vectors
each VF needs. This also allows us to start using MSI-x resources from
the end of the PF's allowed MSI-x vectors so we are less likely to use
entries needed for other features (i.e. RDMA, L2 Offload, etc).
This patch also reworks the ice_res_tracker structure by removing the
search_hint and adding a new member - "end". Instead of having a
search_hint we will always search from 0. The new member, "end", will be
used to manipulate the end of the ice_res_tracker (specifically
sw_irq_tracker) during runtime based on MSI-x vectors needed by SR-IOV.
In the normal case, the end of ice_res_tracker will be equal to the
ice_res_tracker's num_entries.
The sriov_base_vector member was added to the PF structure. It is used
to represent the starting MSI-x index of all the needed MSI-x vectors
for all SR-IOV VFs. Depending on how many MSI-x are needed, SR-IOV may
have to take resources from the sw_irq_tracker. This is done by setting
the sw_irq_tracker->end equal to the pf->sriov_base_vector. When all
SR-IOV VFs are removed then the sw_irq_tracker->end is reset back to
sw_irq_tracker->num_entries. The sriov_base_vector, along with the VF's
number of MSI-x (pf->num_vf_msix), vf_id, and the base MSI-x index on
the PF (pf->hw.func_caps.common_cap.msix_vector_first_id), is used to
calculate the first HW absolute MSI-x index for each VF, which is used
to write to the VPINT_ALLOC[_PCI] and GLINT_VECT2FUNC registers to
program the VFs MSI-x PCI configuration bits. Also, the sriov_base_vector
is used along with VF's num_vf_msix, vf_id, and q_vector->v_idx to
determine the MSI-x register index (used for writing to GLINT_DYN_CTL)
within the PF's space.
Interrupt changes removed any references to hw_base_vector, hw_oicr_idx,
and hw_irq_tracker. Only sw_base_vector, sw_oicr_idx, and sw_irq_tracker
variables remain. Change all of these by removing the "sw_" prefix to
help avoid confusion with these variables and their use.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2019-04-16 10:30:44 -07:00
|
|
|
ice_free_res(pf->irq_tracker, 1, ICE_RES_MISC_VEC_ID);
|
ice: Split irq_tracker into sw_irq_tracker and hw_irq_tracker
For the PF driver, when mapping interrupts to queues, we need to request
IRQs from the kernel and we also have to allocate interrupts from
the device.
Similarly, when the VF driver (iavf.ko) initializes, it requests the kernel
IRQs that it needs but it can't directly allocate interrupts in the device.
Instead, it sends a mailbox message to the ice driver, which then allocates
interrupts in the device on the VF driver's behalf.
Currently both these cases end up having to reserve entries in
pf->irq_tracker but irq_tracker itself is sized based on how many vectors
the PF driver needs. Under the right circumstances, the VF driver can fail
to get entries in irq_tracker, which will result in the VF driver failing
probe.
To fix this, sw_irq_tracker and hw_irq_tracker are introduced. The
sw_irq_tracker tracks only the PF's IRQ request and doesn't play any
role in VF init. hw_irq_tracker represents the device's interrupt space.
When interrupts have to be allocated in the device for either PF or VF,
hw_irq_tracker will be looked up to see if the device has run out of
interrupts.
Signed-off-by: Preethi Banala <preethi.banala@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-09-19 17:23:16 -07:00
|
|
|
pf->num_avail_sw_msix += 1;
|
2018-03-20 07:58:10 -07:00
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:18 -07:00
|
|
|
skip_req_irq:
|
2018-03-20 07:58:10 -07:00
|
|
|
ice_ena_misc_vector(pf);
|
|
|
|
|
ice: Refactor interrupt tracking
Currently we have two MSI-x (IRQ) trackers, one for OS requested MSI-x
entries (sw_irq_tracker) and one for hardware MSI-x vectors
(hw_irq_tracker). Generally the sw_irq_tracker has less entries than the
hw_irq_tracker because the hw_irq_tracker has entries equal to the max
allowed MSI-x per PF and the sw_irq_tracker is mainly the minimum (non
SR-IOV portion of the vectors, kernel granted IRQs). All of the non
SR-IOV portions of the driver (i.e. LAN queues, RDMA queues, OICR, etc.)
take at least one of each type of tracker resource. SR-IOV only grabs
entries from the hw_irq_tracker. There are a few issues with this approach
that can be seen when doing any kind of device reconfiguration (i.e.
ethtool -L, SR-IOV, etc.). One of them being, any time the driver creates
an ice_q_vector and associates it to a LAN queue pair it will grab and
use one entry from the hw_irq_tracker and one from the sw_irq_tracker.
If the indices on these does not match it will cause a Tx timeout, which
will cause a reset and then the indices will match up again and traffic
will resume. The mismatched indices come from the trackers not being the
same size and/or the search_hint in the two trackers not being equal.
Another reason for the refactor is the co-existence of features with
SR-IOV. If SR-IOV is enabled and the interrupts are taken from the end
of the sw_irq_tracker then other features can no longer use this space
because the hardware has now given the remaining interrupts to SR-IOV.
This patch reworks how we track MSI-x vectors by removing the
hw_irq_tracker completely and instead MSI-x resources needed for SR-IOV
are determined all at once instead of per VF. This can be done because
when creating VFs we know how many are wanted and how many MSI-x vectors
each VF needs. This also allows us to start using MSI-x resources from
the end of the PF's allowed MSI-x vectors so we are less likely to use
entries needed for other features (i.e. RDMA, L2 Offload, etc).
This patch also reworks the ice_res_tracker structure by removing the
search_hint and adding a new member - "end". Instead of having a
search_hint we will always search from 0. The new member, "end", will be
used to manipulate the end of the ice_res_tracker (specifically
sw_irq_tracker) during runtime based on MSI-x vectors needed by SR-IOV.
In the normal case, the end of ice_res_tracker will be equal to the
ice_res_tracker's num_entries.
The sriov_base_vector member was added to the PF structure. It is used
to represent the starting MSI-x index of all the needed MSI-x vectors
for all SR-IOV VFs. Depending on how many MSI-x are needed, SR-IOV may
have to take resources from the sw_irq_tracker. This is done by setting
the sw_irq_tracker->end equal to the pf->sriov_base_vector. When all
SR-IOV VFs are removed then the sw_irq_tracker->end is reset back to
sw_irq_tracker->num_entries. The sriov_base_vector, along with the VF's
number of MSI-x (pf->num_vf_msix), vf_id, and the base MSI-x index on
the PF (pf->hw.func_caps.common_cap.msix_vector_first_id), is used to
calculate the first HW absolute MSI-x index for each VF, which is used
to write to the VPINT_ALLOC[_PCI] and GLINT_VECT2FUNC registers to
program the VFs MSI-x PCI configuration bits. Also, the sriov_base_vector
is used along with VF's num_vf_msix, vf_id, and q_vector->v_idx to
determine the MSI-x register index (used for writing to GLINT_DYN_CTL)
within the PF's space.
Interrupt changes removed any references to hw_base_vector, hw_oicr_idx,
and hw_irq_tracker. Only sw_base_vector, sw_oicr_idx, and sw_irq_tracker
variables remain. Change all of these by removing the "sw_" prefix to
help avoid confusion with these variables and their use.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2019-04-16 10:30:44 -07:00
|
|
|
ice_ena_ctrlq_interrupts(hw, pf->oicr_idx);
|
|
|
|
wr32(hw, GLINT_ITR(ICE_RX_ITR, pf->oicr_idx),
|
2018-12-19 10:03:29 -08:00
|
|
|
ITR_REG_ALIGN(ICE_ITR_8K) >> ICE_ITR_GRAN_S);
|
2018-03-20 07:58:10 -07:00
|
|
|
|
|
|
|
ice_flush(hw);
|
2018-03-20 07:58:13 -07:00
|
|
|
ice_irq_dynamic_ena(hw, NULL, NULL);
|
2018-03-20 07:58:10 -07:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:11 -07:00
|
|
|
/**
|
2018-09-19 17:23:09 -07:00
|
|
|
* ice_napi_del - Remove NAPI handler for the VSI
|
|
|
|
* @vsi: VSI for which NAPI handler is to be removed
|
2018-03-20 07:58:11 -07:00
|
|
|
*/
|
2019-04-16 10:24:37 -07:00
|
|
|
static void ice_napi_del(struct ice_vsi *vsi)
|
2018-03-20 07:58:11 -07:00
|
|
|
{
|
2018-09-19 17:23:09 -07:00
|
|
|
int v_idx;
|
2018-03-20 07:58:11 -07:00
|
|
|
|
2018-09-19 17:23:09 -07:00
|
|
|
if (!vsi->netdev)
|
|
|
|
return;
|
2018-03-20 07:58:11 -07:00
|
|
|
|
2019-02-28 15:25:53 -08:00
|
|
|
ice_for_each_q_vector(vsi, v_idx)
|
2018-09-19 17:23:09 -07:00
|
|
|
netif_napi_del(&vsi->q_vectors[v_idx]->napi);
|
2018-03-20 07:58:11 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2018-09-19 17:23:09 -07:00
|
|
|
* ice_napi_add - register NAPI handler for the VSI
|
|
|
|
* @vsi: VSI for which NAPI handler is to be registered
|
2018-03-20 07:58:11 -07:00
|
|
|
*
|
2018-09-19 17:23:09 -07:00
|
|
|
* This function is only called in the driver's load path. Registering the NAPI
|
|
|
|
* handler is done in ice_vsi_alloc_q_vector() for all other cases (i.e. resume,
|
|
|
|
* reset/rebuild, etc.)
|
2018-03-20 07:58:11 -07:00
|
|
|
*/
|
2018-09-19 17:23:09 -07:00
|
|
|
static void ice_napi_add(struct ice_vsi *vsi)
|
2018-03-20 07:58:11 -07:00
|
|
|
{
|
2018-09-19 17:23:09 -07:00
|
|
|
int v_idx;
|
2018-03-20 07:58:11 -07:00
|
|
|
|
2018-09-19 17:23:09 -07:00
|
|
|
if (!vsi->netdev)
|
2018-03-20 07:58:11 -07:00
|
|
|
return;
|
|
|
|
|
2019-02-28 15:25:53 -08:00
|
|
|
ice_for_each_q_vector(vsi, v_idx)
|
2018-09-19 17:23:09 -07:00
|
|
|
netif_napi_add(vsi->netdev, &vsi->q_vectors[v_idx]->napi,
|
|
|
|
ice_napi_poll, NAPI_POLL_WEIGHT);
|
2018-03-20 07:58:11 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2018-09-19 17:23:09 -07:00
|
|
|
* ice_cfg_netdev - Allocate, configure and register a netdev
|
|
|
|
* @vsi: the VSI associated with the new netdev
|
2018-03-20 07:58:11 -07:00
|
|
|
*
|
|
|
|
* Returns 0 on success, negative value on failure
|
|
|
|
*/
|
|
|
|
static int ice_cfg_netdev(struct ice_vsi *vsi)
|
|
|
|
{
|
2018-03-20 07:58:15 -07:00
|
|
|
netdev_features_t csumo_features;
|
|
|
|
netdev_features_t vlano_features;
|
|
|
|
netdev_features_t dflt_features;
|
|
|
|
netdev_features_t tso_features;
|
2018-03-20 07:58:11 -07:00
|
|
|
struct ice_netdev_priv *np;
|
|
|
|
struct net_device *netdev;
|
|
|
|
u8 mac_addr[ETH_ALEN];
|
2018-09-19 17:23:09 -07:00
|
|
|
int err;
|
2018-03-20 07:58:11 -07:00
|
|
|
|
2019-02-08 12:50:31 -08:00
|
|
|
netdev = alloc_etherdev_mqs(sizeof(*np), vsi->alloc_txq,
|
|
|
|
vsi->alloc_rxq);
|
2018-03-20 07:58:11 -07:00
|
|
|
if (!netdev)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
vsi->netdev = netdev;
|
|
|
|
np = netdev_priv(netdev);
|
|
|
|
np->vsi = vsi;
|
|
|
|
|
2018-03-20 07:58:15 -07:00
|
|
|
dflt_features = NETIF_F_SG |
|
|
|
|
NETIF_F_HIGHDMA |
|
|
|
|
NETIF_F_RXHASH;
|
|
|
|
|
|
|
|
csumo_features = NETIF_F_RXCSUM |
|
|
|
|
NETIF_F_IP_CSUM |
|
2018-12-19 10:03:32 -08:00
|
|
|
NETIF_F_SCTP_CRC |
|
2018-03-20 07:58:15 -07:00
|
|
|
NETIF_F_IPV6_CSUM;
|
|
|
|
|
|
|
|
vlano_features = NETIF_F_HW_VLAN_CTAG_FILTER |
|
|
|
|
NETIF_F_HW_VLAN_CTAG_TX |
|
|
|
|
NETIF_F_HW_VLAN_CTAG_RX;
|
|
|
|
|
|
|
|
tso_features = NETIF_F_TSO;
|
|
|
|
|
2018-03-20 07:58:11 -07:00
|
|
|
/* set features that user can change */
|
2018-03-20 07:58:15 -07:00
|
|
|
netdev->hw_features = dflt_features | csumo_features |
|
|
|
|
vlano_features | tso_features;
|
2018-03-20 07:58:11 -07:00
|
|
|
|
|
|
|
/* enable features */
|
|
|
|
netdev->features |= netdev->hw_features;
|
2018-03-20 07:58:15 -07:00
|
|
|
/* encap and VLAN devices inherit default, csumo and tso features */
|
|
|
|
netdev->hw_enc_features |= dflt_features | csumo_features |
|
|
|
|
tso_features;
|
|
|
|
netdev->vlan_features |= dflt_features | csumo_features |
|
|
|
|
tso_features;
|
2018-03-20 07:58:11 -07:00
|
|
|
|
|
|
|
if (vsi->type == ICE_VSI_PF) {
|
|
|
|
SET_NETDEV_DEV(netdev, &vsi->back->pdev->dev);
|
|
|
|
ether_addr_copy(mac_addr, vsi->port_info->mac.perm_addr);
|
|
|
|
|
|
|
|
ether_addr_copy(netdev->dev_addr, mac_addr);
|
|
|
|
ether_addr_copy(netdev->perm_addr, mac_addr);
|
|
|
|
}
|
|
|
|
|
|
|
|
netdev->priv_flags |= IFF_UNICAST_FLT;
|
|
|
|
|
2018-03-20 07:58:13 -07:00
|
|
|
/* assign netdev_ops */
|
|
|
|
netdev->netdev_ops = &ice_netdev_ops;
|
|
|
|
|
2018-03-20 07:58:11 -07:00
|
|
|
/* setup watchdog timeout value to be 5 second */
|
|
|
|
netdev->watchdog_timeo = 5 * HZ;
|
|
|
|
|
2018-03-20 07:58:16 -07:00
|
|
|
ice_set_ethtool_ops(netdev);
|
|
|
|
|
2018-03-20 07:58:11 -07:00
|
|
|
netdev->min_mtu = ETH_MIN_MTU;
|
|
|
|
netdev->max_mtu = ICE_MAX_MTU;
|
|
|
|
|
2018-09-19 17:23:09 -07:00
|
|
|
err = register_netdev(vsi->netdev);
|
|
|
|
if (err)
|
|
|
|
return err;
|
2018-03-20 07:58:11 -07:00
|
|
|
|
2018-09-19 17:23:09 -07:00
|
|
|
netif_carrier_off(vsi->netdev);
|
2018-03-20 07:58:11 -07:00
|
|
|
|
2018-09-19 17:23:09 -07:00
|
|
|
/* make sure transmit queues start off as stopped */
|
|
|
|
netif_tx_stop_all_queues(vsi->netdev);
|
2018-03-20 07:58:11 -07:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:15 -07:00
|
|
|
/**
|
|
|
|
* ice_fill_rss_lut - Fill the RSS lookup table with default values
|
|
|
|
* @lut: Lookup table
|
|
|
|
* @rss_table_size: Lookup table size
|
|
|
|
* @rss_size: Range of queue number for hashing
|
|
|
|
*/
|
|
|
|
void ice_fill_rss_lut(u8 *lut, u16 rss_table_size, u16 rss_size)
|
|
|
|
{
|
|
|
|
u16 i;
|
|
|
|
|
|
|
|
for (i = 0; i < rss_table_size; i++)
|
|
|
|
lut[i] = i % rss_size;
|
|
|
|
}
|
|
|
|
|
2018-08-09 06:29:50 -07:00
|
|
|
/**
|
|
|
|
* ice_pf_vsi_setup - Set up a PF VSI
|
|
|
|
* @pf: board private structure
|
|
|
|
* @pi: pointer to the port_info instance
|
|
|
|
*
|
2019-04-16 10:30:43 -07:00
|
|
|
* Returns pointer to the successfully allocated VSI software struct
|
|
|
|
* on success, otherwise returns NULL on failure.
|
2018-08-09 06:29:50 -07:00
|
|
|
*/
|
|
|
|
static struct ice_vsi *
|
|
|
|
ice_pf_vsi_setup(struct ice_pf *pf, struct ice_port_info *pi)
|
|
|
|
{
|
|
|
|
return ice_vsi_setup(pf, pi, ICE_VSI_PF, ICE_INVAL_VFID);
|
|
|
|
}
|
|
|
|
|
2019-04-16 10:30:43 -07:00
|
|
|
/**
|
|
|
|
* ice_lb_vsi_setup - Set up a loopback VSI
|
|
|
|
* @pf: board private structure
|
|
|
|
* @pi: pointer to the port_info instance
|
|
|
|
*
|
|
|
|
* Returns pointer to the successfully allocated VSI software struct
|
|
|
|
* on success, otherwise returns NULL on failure.
|
|
|
|
*/
|
|
|
|
struct ice_vsi *
|
|
|
|
ice_lb_vsi_setup(struct ice_pf *pf, struct ice_port_info *pi)
|
|
|
|
{
|
|
|
|
return ice_vsi_setup(pf, pi, ICE_VSI_LB, ICE_INVAL_VFID);
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:15 -07:00
|
|
|
/**
|
2019-02-19 15:04:13 -08:00
|
|
|
* ice_vlan_rx_add_vid - Add a VLAN ID filter to HW offload
|
2018-03-20 07:58:15 -07:00
|
|
|
* @netdev: network interface to be adjusted
|
|
|
|
* @proto: unused protocol
|
2019-02-19 15:04:13 -08:00
|
|
|
* @vid: VLAN ID to be added
|
2018-03-20 07:58:15 -07:00
|
|
|
*
|
2019-02-19 15:04:13 -08:00
|
|
|
* net_device_ops implementation for adding VLAN IDs
|
2018-03-20 07:58:15 -07:00
|
|
|
*/
|
2019-02-26 16:35:11 -08:00
|
|
|
static int
|
|
|
|
ice_vlan_rx_add_vid(struct net_device *netdev, __always_unused __be16 proto,
|
|
|
|
u16 vid)
|
2018-03-20 07:58:15 -07:00
|
|
|
{
|
|
|
|
struct ice_netdev_priv *np = netdev_priv(netdev);
|
|
|
|
struct ice_vsi *vsi = np->vsi;
|
2019-02-26 16:35:14 -08:00
|
|
|
int ret;
|
2018-03-20 07:58:15 -07:00
|
|
|
|
|
|
|
if (vid >= VLAN_N_VID) {
|
|
|
|
netdev_err(netdev, "VLAN id requested %d is out of range %d\n",
|
|
|
|
vid, VLAN_N_VID);
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (vsi->info.pvid)
|
|
|
|
return -EINVAL;
|
|
|
|
|
2018-08-09 06:29:56 -07:00
|
|
|
/* Enable VLAN pruning when VLAN 0 is added */
|
|
|
|
if (unlikely(!vid)) {
|
2019-02-26 16:35:14 -08:00
|
|
|
ret = ice_cfg_vlan_pruning(vsi, true, false);
|
2018-08-09 06:29:56 -07:00
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2019-02-19 15:04:13 -08:00
|
|
|
/* Add all VLAN IDs including 0 to the switch filter. VLAN ID 0 is
|
2018-03-20 07:58:15 -07:00
|
|
|
* needed to continue allowing all untagged packets since VLAN prune
|
|
|
|
* list is applied to all packets by the switch
|
|
|
|
*/
|
2019-02-26 16:35:14 -08:00
|
|
|
ret = ice_vsi_add_vlan(vsi, vid);
|
|
|
|
if (!ret) {
|
|
|
|
vsi->vlan_ena = true;
|
|
|
|
set_bit(ICE_VSI_FLAG_VLAN_FLTR_CHANGED, vsi->flags);
|
|
|
|
}
|
|
|
|
|
|
|
|
return ret;
|
2018-03-20 07:58:15 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2019-02-19 15:04:13 -08:00
|
|
|
* ice_vlan_rx_kill_vid - Remove a VLAN ID filter from HW offload
|
2018-03-20 07:58:15 -07:00
|
|
|
* @netdev: network interface to be adjusted
|
|
|
|
* @proto: unused protocol
|
2019-02-19 15:04:13 -08:00
|
|
|
* @vid: VLAN ID to be removed
|
2018-03-20 07:58:15 -07:00
|
|
|
*
|
2019-02-19 15:04:13 -08:00
|
|
|
* net_device_ops implementation for removing VLAN IDs
|
2018-03-20 07:58:15 -07:00
|
|
|
*/
|
2019-02-26 16:35:11 -08:00
|
|
|
static int
|
|
|
|
ice_vlan_rx_kill_vid(struct net_device *netdev, __always_unused __be16 proto,
|
|
|
|
u16 vid)
|
2018-03-20 07:58:15 -07:00
|
|
|
{
|
|
|
|
struct ice_netdev_priv *np = netdev_priv(netdev);
|
|
|
|
struct ice_vsi *vsi = np->vsi;
|
2019-02-26 16:35:14 -08:00
|
|
|
int ret;
|
2018-03-20 07:58:15 -07:00
|
|
|
|
|
|
|
if (vsi->info.pvid)
|
|
|
|
return -EINVAL;
|
|
|
|
|
2018-08-09 06:29:56 -07:00
|
|
|
/* Make sure ice_vsi_kill_vlan is successful before updating VLAN
|
|
|
|
* information
|
2018-03-20 07:58:15 -07:00
|
|
|
*/
|
2019-02-26 16:35:14 -08:00
|
|
|
ret = ice_vsi_kill_vlan(vsi, vid);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
2018-03-20 07:58:15 -07:00
|
|
|
|
2018-08-09 06:29:56 -07:00
|
|
|
/* Disable VLAN pruning when VLAN 0 is removed */
|
|
|
|
if (unlikely(!vid))
|
2019-02-26 16:35:14 -08:00
|
|
|
ret = ice_cfg_vlan_pruning(vsi, false, false);
|
2018-08-09 06:29:56 -07:00
|
|
|
|
2019-02-26 16:35:14 -08:00
|
|
|
vsi->vlan_ena = false;
|
|
|
|
set_bit(ICE_VSI_FLAG_VLAN_FLTR_CHANGED, vsi->flags);
|
|
|
|
return ret;
|
2018-03-20 07:58:15 -07:00
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:11 -07:00
|
|
|
/**
|
|
|
|
* ice_setup_pf_sw - Setup the HW switch on startup or after reset
|
|
|
|
* @pf: board private structure
|
|
|
|
*
|
|
|
|
* Returns 0 on success, negative value on failure
|
|
|
|
*/
|
|
|
|
static int ice_setup_pf_sw(struct ice_pf *pf)
|
|
|
|
{
|
ice: Add support for switch filter programming
A VSI needs traffic directed towards it. This is done by programming
filter rules on the switch (embedded vSwitch) element in the hardware,
which connects the VSI to the ingress/egress port.
This patch introduces data structures and functions necessary to add
remove or update switch rules on the switch element. This is a pretty low
level function that is generic enough to add a whole range of filters.
This patch also introduces two top level functions ice_add_mac and
ice_remove mac which through a series of intermediate helper functions
eventually call ice_aq_sw_rules to add/delete simple MAC based filters.
It's worth noting that one invocation of ice_add_mac/ice_remove_mac
is capable of adding/deleting multiple MAC filters.
Also worth noting is the fact that the driver maintains a list of currently
active filters, so every filter addition/removal causes an update to this
list. This is done for a couple of reasons:
1) If two VSIs try to add the same filters, we need to detect it and do
things a little differently (i.e. use VSI lists, described below) as
the same filter can't be added more than once.
2) In the event of a hardware reset we can simply walk through this list
and restore the filters.
VSI Lists:
In a multi-VSI situation, it's possible that multiple VSIs want to add the
same filter rule. For example, two VSIs that want to receive broadcast
traffic would both add a filter for destination MAC ff:ff:ff:ff:ff:ff.
This can become cumbersome to maintain and so this is handled using a
VSI list.
A VSI list is resource that can be allocated in the hardware using the
ice_aq_alloc_free_res admin queue command. Simply put, a VSI list can
be thought of as a subscription list containing a set of VSIs to which
the packet should be forwarded, should the filter match.
For example, if VSI-0 has already added a broadcast filter, and VSI-1
wants to do the same thing, the filter creation flow will detect this,
allocate a VSI list and update the switch rule so that broadcast traffic
will now be forwarded to the VSI list which contains VSI-0 and VSI-1.
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:12 -07:00
|
|
|
LIST_HEAD(tmp_add_list);
|
|
|
|
u8 broadcast[ETH_ALEN];
|
2018-03-20 07:58:11 -07:00
|
|
|
struct ice_vsi *vsi;
|
|
|
|
int status = 0;
|
|
|
|
|
2018-09-19 17:23:11 -07:00
|
|
|
if (ice_is_reset_in_progress(pf->state))
|
2018-08-09 06:29:50 -07:00
|
|
|
return -EBUSY;
|
|
|
|
|
|
|
|
vsi = ice_pf_vsi_setup(pf, pf->hw.port_info);
|
|
|
|
if (!vsi) {
|
|
|
|
status = -ENOMEM;
|
|
|
|
goto unroll_vsi_setup;
|
2018-03-20 07:58:11 -07:00
|
|
|
}
|
|
|
|
|
2018-09-19 17:23:09 -07:00
|
|
|
status = ice_cfg_netdev(vsi);
|
|
|
|
if (status) {
|
|
|
|
status = -ENODEV;
|
|
|
|
goto unroll_vsi_setup;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* registering the NAPI handler requires both the queues and
|
|
|
|
* netdev to be created, which are done in ice_pf_vsi_setup()
|
|
|
|
* and ice_cfg_netdev() respectively
|
|
|
|
*/
|
|
|
|
ice_napi_add(vsi);
|
|
|
|
|
2018-08-09 06:29:50 -07:00
|
|
|
/* To add a MAC filter, first add the MAC to a list and then
|
|
|
|
* pass the list to ice_add_mac.
|
ice: Add support for switch filter programming
A VSI needs traffic directed towards it. This is done by programming
filter rules on the switch (embedded vSwitch) element in the hardware,
which connects the VSI to the ingress/egress port.
This patch introduces data structures and functions necessary to add
remove or update switch rules on the switch element. This is a pretty low
level function that is generic enough to add a whole range of filters.
This patch also introduces two top level functions ice_add_mac and
ice_remove mac which through a series of intermediate helper functions
eventually call ice_aq_sw_rules to add/delete simple MAC based filters.
It's worth noting that one invocation of ice_add_mac/ice_remove_mac
is capable of adding/deleting multiple MAC filters.
Also worth noting is the fact that the driver maintains a list of currently
active filters, so every filter addition/removal causes an update to this
list. This is done for a couple of reasons:
1) If two VSIs try to add the same filters, we need to detect it and do
things a little differently (i.e. use VSI lists, described below) as
the same filter can't be added more than once.
2) In the event of a hardware reset we can simply walk through this list
and restore the filters.
VSI Lists:
In a multi-VSI situation, it's possible that multiple VSIs want to add the
same filter rule. For example, two VSIs that want to receive broadcast
traffic would both add a filter for destination MAC ff:ff:ff:ff:ff:ff.
This can become cumbersome to maintain and so this is handled using a
VSI list.
A VSI list is resource that can be allocated in the hardware using the
ice_aq_alloc_free_res admin queue command. Simply put, a VSI list can
be thought of as a subscription list containing a set of VSIs to which
the packet should be forwarded, should the filter match.
For example, if VSI-0 has already added a broadcast filter, and VSI-1
wants to do the same thing, the filter creation flow will detect this,
allocate a VSI list and update the switch rule so that broadcast traffic
will now be forwarded to the VSI list which contains VSI-0 and VSI-1.
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:12 -07:00
|
|
|
*/
|
2018-08-09 06:29:50 -07:00
|
|
|
|
|
|
|
/* Add a unicast MAC filter so the VSI can get its packets */
|
ice: Add support for switch filter programming
A VSI needs traffic directed towards it. This is done by programming
filter rules on the switch (embedded vSwitch) element in the hardware,
which connects the VSI to the ingress/egress port.
This patch introduces data structures and functions necessary to add
remove or update switch rules on the switch element. This is a pretty low
level function that is generic enough to add a whole range of filters.
This patch also introduces two top level functions ice_add_mac and
ice_remove mac which through a series of intermediate helper functions
eventually call ice_aq_sw_rules to add/delete simple MAC based filters.
It's worth noting that one invocation of ice_add_mac/ice_remove_mac
is capable of adding/deleting multiple MAC filters.
Also worth noting is the fact that the driver maintains a list of currently
active filters, so every filter addition/removal causes an update to this
list. This is done for a couple of reasons:
1) If two VSIs try to add the same filters, we need to detect it and do
things a little differently (i.e. use VSI lists, described below) as
the same filter can't be added more than once.
2) In the event of a hardware reset we can simply walk through this list
and restore the filters.
VSI Lists:
In a multi-VSI situation, it's possible that multiple VSIs want to add the
same filter rule. For example, two VSIs that want to receive broadcast
traffic would both add a filter for destination MAC ff:ff:ff:ff:ff:ff.
This can become cumbersome to maintain and so this is handled using a
VSI list.
A VSI list is resource that can be allocated in the hardware using the
ice_aq_alloc_free_res admin queue command. Simply put, a VSI list can
be thought of as a subscription list containing a set of VSIs to which
the packet should be forwarded, should the filter match.
For example, if VSI-0 has already added a broadcast filter, and VSI-1
wants to do the same thing, the filter creation flow will detect this,
allocate a VSI list and update the switch rule so that broadcast traffic
will now be forwarded to the VSI list which contains VSI-0 and VSI-1.
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:12 -07:00
|
|
|
status = ice_add_mac_to_list(vsi, &tmp_add_list,
|
|
|
|
vsi->port_info->mac.perm_addr);
|
|
|
|
if (status)
|
2018-09-19 17:23:09 -07:00
|
|
|
goto unroll_napi_add;
|
ice: Add support for switch filter programming
A VSI needs traffic directed towards it. This is done by programming
filter rules on the switch (embedded vSwitch) element in the hardware,
which connects the VSI to the ingress/egress port.
This patch introduces data structures and functions necessary to add
remove or update switch rules on the switch element. This is a pretty low
level function that is generic enough to add a whole range of filters.
This patch also introduces two top level functions ice_add_mac and
ice_remove mac which through a series of intermediate helper functions
eventually call ice_aq_sw_rules to add/delete simple MAC based filters.
It's worth noting that one invocation of ice_add_mac/ice_remove_mac
is capable of adding/deleting multiple MAC filters.
Also worth noting is the fact that the driver maintains a list of currently
active filters, so every filter addition/removal causes an update to this
list. This is done for a couple of reasons:
1) If two VSIs try to add the same filters, we need to detect it and do
things a little differently (i.e. use VSI lists, described below) as
the same filter can't be added more than once.
2) In the event of a hardware reset we can simply walk through this list
and restore the filters.
VSI Lists:
In a multi-VSI situation, it's possible that multiple VSIs want to add the
same filter rule. For example, two VSIs that want to receive broadcast
traffic would both add a filter for destination MAC ff:ff:ff:ff:ff:ff.
This can become cumbersome to maintain and so this is handled using a
VSI list.
A VSI list is resource that can be allocated in the hardware using the
ice_aq_alloc_free_res admin queue command. Simply put, a VSI list can
be thought of as a subscription list containing a set of VSIs to which
the packet should be forwarded, should the filter match.
For example, if VSI-0 has already added a broadcast filter, and VSI-1
wants to do the same thing, the filter creation flow will detect this,
allocate a VSI list and update the switch rule so that broadcast traffic
will now be forwarded to the VSI list which contains VSI-0 and VSI-1.
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:12 -07:00
|
|
|
|
|
|
|
/* VSI needs to receive broadcast traffic, so add the broadcast
|
2018-08-09 06:29:50 -07:00
|
|
|
* MAC address to the list as well.
|
ice: Add support for switch filter programming
A VSI needs traffic directed towards it. This is done by programming
filter rules on the switch (embedded vSwitch) element in the hardware,
which connects the VSI to the ingress/egress port.
This patch introduces data structures and functions necessary to add
remove or update switch rules on the switch element. This is a pretty low
level function that is generic enough to add a whole range of filters.
This patch also introduces two top level functions ice_add_mac and
ice_remove mac which through a series of intermediate helper functions
eventually call ice_aq_sw_rules to add/delete simple MAC based filters.
It's worth noting that one invocation of ice_add_mac/ice_remove_mac
is capable of adding/deleting multiple MAC filters.
Also worth noting is the fact that the driver maintains a list of currently
active filters, so every filter addition/removal causes an update to this
list. This is done for a couple of reasons:
1) If two VSIs try to add the same filters, we need to detect it and do
things a little differently (i.e. use VSI lists, described below) as
the same filter can't be added more than once.
2) In the event of a hardware reset we can simply walk through this list
and restore the filters.
VSI Lists:
In a multi-VSI situation, it's possible that multiple VSIs want to add the
same filter rule. For example, two VSIs that want to receive broadcast
traffic would both add a filter for destination MAC ff:ff:ff:ff:ff:ff.
This can become cumbersome to maintain and so this is handled using a
VSI list.
A VSI list is resource that can be allocated in the hardware using the
ice_aq_alloc_free_res admin queue command. Simply put, a VSI list can
be thought of as a subscription list containing a set of VSIs to which
the packet should be forwarded, should the filter match.
For example, if VSI-0 has already added a broadcast filter, and VSI-1
wants to do the same thing, the filter creation flow will detect this,
allocate a VSI list and update the switch rule so that broadcast traffic
will now be forwarded to the VSI list which contains VSI-0 and VSI-1.
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:12 -07:00
|
|
|
*/
|
|
|
|
eth_broadcast_addr(broadcast);
|
|
|
|
status = ice_add_mac_to_list(vsi, &tmp_add_list, broadcast);
|
|
|
|
if (status)
|
2018-08-09 06:29:50 -07:00
|
|
|
goto free_mac_list;
|
ice: Add support for switch filter programming
A VSI needs traffic directed towards it. This is done by programming
filter rules on the switch (embedded vSwitch) element in the hardware,
which connects the VSI to the ingress/egress port.
This patch introduces data structures and functions necessary to add
remove or update switch rules on the switch element. This is a pretty low
level function that is generic enough to add a whole range of filters.
This patch also introduces two top level functions ice_add_mac and
ice_remove mac which through a series of intermediate helper functions
eventually call ice_aq_sw_rules to add/delete simple MAC based filters.
It's worth noting that one invocation of ice_add_mac/ice_remove_mac
is capable of adding/deleting multiple MAC filters.
Also worth noting is the fact that the driver maintains a list of currently
active filters, so every filter addition/removal causes an update to this
list. This is done for a couple of reasons:
1) If two VSIs try to add the same filters, we need to detect it and do
things a little differently (i.e. use VSI lists, described below) as
the same filter can't be added more than once.
2) In the event of a hardware reset we can simply walk through this list
and restore the filters.
VSI Lists:
In a multi-VSI situation, it's possible that multiple VSIs want to add the
same filter rule. For example, two VSIs that want to receive broadcast
traffic would both add a filter for destination MAC ff:ff:ff:ff:ff:ff.
This can become cumbersome to maintain and so this is handled using a
VSI list.
A VSI list is resource that can be allocated in the hardware using the
ice_aq_alloc_free_res admin queue command. Simply put, a VSI list can
be thought of as a subscription list containing a set of VSIs to which
the packet should be forwarded, should the filter match.
For example, if VSI-0 has already added a broadcast filter, and VSI-1
wants to do the same thing, the filter creation flow will detect this,
allocate a VSI list and update the switch rule so that broadcast traffic
will now be forwarded to the VSI list which contains VSI-0 and VSI-1.
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:12 -07:00
|
|
|
|
|
|
|
/* program MAC filters for entries in tmp_add_list */
|
|
|
|
status = ice_add_mac(&pf->hw, &tmp_add_list);
|
|
|
|
if (status) {
|
|
|
|
dev_err(&pf->pdev->dev, "Could not add MAC filters\n");
|
|
|
|
status = -ENOMEM;
|
2018-08-09 06:29:50 -07:00
|
|
|
goto free_mac_list;
|
ice: Add support for switch filter programming
A VSI needs traffic directed towards it. This is done by programming
filter rules on the switch (embedded vSwitch) element in the hardware,
which connects the VSI to the ingress/egress port.
This patch introduces data structures and functions necessary to add
remove or update switch rules on the switch element. This is a pretty low
level function that is generic enough to add a whole range of filters.
This patch also introduces two top level functions ice_add_mac and
ice_remove mac which through a series of intermediate helper functions
eventually call ice_aq_sw_rules to add/delete simple MAC based filters.
It's worth noting that one invocation of ice_add_mac/ice_remove_mac
is capable of adding/deleting multiple MAC filters.
Also worth noting is the fact that the driver maintains a list of currently
active filters, so every filter addition/removal causes an update to this
list. This is done for a couple of reasons:
1) If two VSIs try to add the same filters, we need to detect it and do
things a little differently (i.e. use VSI lists, described below) as
the same filter can't be added more than once.
2) In the event of a hardware reset we can simply walk through this list
and restore the filters.
VSI Lists:
In a multi-VSI situation, it's possible that multiple VSIs want to add the
same filter rule. For example, two VSIs that want to receive broadcast
traffic would both add a filter for destination MAC ff:ff:ff:ff:ff:ff.
This can become cumbersome to maintain and so this is handled using a
VSI list.
A VSI list is resource that can be allocated in the hardware using the
ice_aq_alloc_free_res admin queue command. Simply put, a VSI list can
be thought of as a subscription list containing a set of VSIs to which
the packet should be forwarded, should the filter match.
For example, if VSI-0 has already added a broadcast filter, and VSI-1
wants to do the same thing, the filter creation flow will detect this,
allocate a VSI list and update the switch rule so that broadcast traffic
will now be forwarded to the VSI list which contains VSI-0 and VSI-1.
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:12 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
ice_free_fltr_list(&pf->pdev->dev, &tmp_add_list);
|
|
|
|
return status;
|
|
|
|
|
2018-08-09 06:29:50 -07:00
|
|
|
free_mac_list:
|
ice: Add support for switch filter programming
A VSI needs traffic directed towards it. This is done by programming
filter rules on the switch (embedded vSwitch) element in the hardware,
which connects the VSI to the ingress/egress port.
This patch introduces data structures and functions necessary to add
remove or update switch rules on the switch element. This is a pretty low
level function that is generic enough to add a whole range of filters.
This patch also introduces two top level functions ice_add_mac and
ice_remove mac which through a series of intermediate helper functions
eventually call ice_aq_sw_rules to add/delete simple MAC based filters.
It's worth noting that one invocation of ice_add_mac/ice_remove_mac
is capable of adding/deleting multiple MAC filters.
Also worth noting is the fact that the driver maintains a list of currently
active filters, so every filter addition/removal causes an update to this
list. This is done for a couple of reasons:
1) If two VSIs try to add the same filters, we need to detect it and do
things a little differently (i.e. use VSI lists, described below) as
the same filter can't be added more than once.
2) In the event of a hardware reset we can simply walk through this list
and restore the filters.
VSI Lists:
In a multi-VSI situation, it's possible that multiple VSIs want to add the
same filter rule. For example, two VSIs that want to receive broadcast
traffic would both add a filter for destination MAC ff:ff:ff:ff:ff:ff.
This can become cumbersome to maintain and so this is handled using a
VSI list.
A VSI list is resource that can be allocated in the hardware using the
ice_aq_alloc_free_res admin queue command. Simply put, a VSI list can
be thought of as a subscription list containing a set of VSIs to which
the packet should be forwarded, should the filter match.
For example, if VSI-0 has already added a broadcast filter, and VSI-1
wants to do the same thing, the filter creation flow will detect this,
allocate a VSI list and update the switch rule so that broadcast traffic
will now be forwarded to the VSI list which contains VSI-0 and VSI-1.
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:12 -07:00
|
|
|
ice_free_fltr_list(&pf->pdev->dev, &tmp_add_list);
|
|
|
|
|
2018-09-19 17:23:09 -07:00
|
|
|
unroll_napi_add:
|
2018-03-20 07:58:11 -07:00
|
|
|
if (vsi) {
|
2018-09-19 17:23:09 -07:00
|
|
|
ice_napi_del(vsi);
|
2018-03-20 07:58:11 -07:00
|
|
|
if (vsi->netdev) {
|
2018-09-19 17:23:09 -07:00
|
|
|
if (vsi->netdev->reg_state == NETREG_REGISTERED)
|
|
|
|
unregister_netdev(vsi->netdev);
|
2018-03-20 07:58:11 -07:00
|
|
|
free_netdev(vsi->netdev);
|
|
|
|
vsi->netdev = NULL;
|
|
|
|
}
|
2018-09-19 17:23:09 -07:00
|
|
|
}
|
ice: Add support for switch filter programming
A VSI needs traffic directed towards it. This is done by programming
filter rules on the switch (embedded vSwitch) element in the hardware,
which connects the VSI to the ingress/egress port.
This patch introduces data structures and functions necessary to add
remove or update switch rules on the switch element. This is a pretty low
level function that is generic enough to add a whole range of filters.
This patch also introduces two top level functions ice_add_mac and
ice_remove mac which through a series of intermediate helper functions
eventually call ice_aq_sw_rules to add/delete simple MAC based filters.
It's worth noting that one invocation of ice_add_mac/ice_remove_mac
is capable of adding/deleting multiple MAC filters.
Also worth noting is the fact that the driver maintains a list of currently
active filters, so every filter addition/removal causes an update to this
list. This is done for a couple of reasons:
1) If two VSIs try to add the same filters, we need to detect it and do
things a little differently (i.e. use VSI lists, described below) as
the same filter can't be added more than once.
2) In the event of a hardware reset we can simply walk through this list
and restore the filters.
VSI Lists:
In a multi-VSI situation, it's possible that multiple VSIs want to add the
same filter rule. For example, two VSIs that want to receive broadcast
traffic would both add a filter for destination MAC ff:ff:ff:ff:ff:ff.
This can become cumbersome to maintain and so this is handled using a
VSI list.
A VSI list is resource that can be allocated in the hardware using the
ice_aq_alloc_free_res admin queue command. Simply put, a VSI list can
be thought of as a subscription list containing a set of VSIs to which
the packet should be forwarded, should the filter match.
For example, if VSI-0 has already added a broadcast filter, and VSI-1
wants to do the same thing, the filter creation flow will detect this,
allocate a VSI list and update the switch rule so that broadcast traffic
will now be forwarded to the VSI list which contains VSI-0 and VSI-1.
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:12 -07:00
|
|
|
|
2018-09-19 17:23:09 -07:00
|
|
|
unroll_vsi_setup:
|
|
|
|
if (vsi) {
|
|
|
|
ice_vsi_free_q_vectors(vsi);
|
2018-03-20 07:58:11 -07:00
|
|
|
ice_vsi_delete(vsi);
|
|
|
|
ice_vsi_put_qs(vsi);
|
|
|
|
pf->q_left_tx += vsi->alloc_txq;
|
|
|
|
pf->q_left_rx += vsi->alloc_rxq;
|
|
|
|
ice_vsi_clear(vsi);
|
|
|
|
}
|
|
|
|
return status;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
/**
|
|
|
|
* ice_determine_q_usage - Calculate queue distribution
|
|
|
|
* @pf: board private structure
|
|
|
|
*
|
|
|
|
* Return -ENOMEM if we don't get enough queues for all ports
|
|
|
|
*/
|
|
|
|
static void ice_determine_q_usage(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
u16 q_left_tx, q_left_rx;
|
|
|
|
|
|
|
|
q_left_tx = pf->hw.func_caps.common_cap.num_txq;
|
|
|
|
q_left_rx = pf->hw.func_caps.common_cap.num_rxq;
|
|
|
|
|
2018-03-20 07:58:17 -07:00
|
|
|
pf->num_lan_tx = min_t(int, q_left_tx, num_online_cpus());
|
2018-03-20 07:58:15 -07:00
|
|
|
|
2018-10-26 11:44:47 -07:00
|
|
|
/* only 1 Rx queue unless RSS is enabled */
|
2018-03-20 07:58:15 -07:00
|
|
|
if (!test_bit(ICE_FLAG_RSS_ENA, pf->flags))
|
|
|
|
pf->num_lan_rx = 1;
|
|
|
|
else
|
|
|
|
pf->num_lan_rx = min_t(int, q_left_rx, num_online_cpus());
|
2018-03-20 07:58:10 -07:00
|
|
|
|
|
|
|
pf->q_left_tx = q_left_tx - pf->num_lan_tx;
|
|
|
|
pf->q_left_rx = q_left_rx - pf->num_lan_rx;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_deinit_pf - Unrolls initialziations done by ice_init_pf
|
|
|
|
* @pf: board private structure to initialize
|
|
|
|
*/
|
|
|
|
static void ice_deinit_pf(struct ice_pf *pf)
|
|
|
|
{
|
2018-08-09 06:29:57 -07:00
|
|
|
ice_service_task_stop(pf);
|
2018-03-20 07:58:10 -07:00
|
|
|
mutex_destroy(&pf->sw_mutex);
|
|
|
|
mutex_destroy(&pf->avail_q_mutex);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_init_pf - Initialize general software structures (struct ice_pf)
|
|
|
|
* @pf: board private structure to initialize
|
|
|
|
*/
|
|
|
|
static void ice_init_pf(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
bitmap_zero(pf->flags, ICE_PF_FLAGS_NBITS);
|
|
|
|
set_bit(ICE_FLAG_MSIX_ENA, pf->flags);
|
2018-09-19 17:42:54 -07:00
|
|
|
#ifdef CONFIG_PCI_IOV
|
|
|
|
if (pf->hw.func_caps.common_cap.sr_iov_1_1) {
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
|
|
|
|
set_bit(ICE_FLAG_SRIOV_CAPABLE, pf->flags);
|
|
|
|
pf->num_vfs_supported = min_t(int, hw->func_caps.num_allocd_vfs,
|
|
|
|
ICE_MAX_VF_COUNT);
|
|
|
|
}
|
|
|
|
#endif /* CONFIG_PCI_IOV */
|
2018-03-20 07:58:10 -07:00
|
|
|
|
|
|
|
mutex_init(&pf->sw_mutex);
|
|
|
|
mutex_init(&pf->avail_q_mutex);
|
|
|
|
|
|
|
|
/* Clear avail_[t|r]x_qs bitmaps (set all to avail) */
|
|
|
|
mutex_lock(&pf->avail_q_mutex);
|
|
|
|
bitmap_zero(pf->avail_txqs, ICE_MAX_TXQS);
|
|
|
|
bitmap_zero(pf->avail_rxqs, ICE_MAX_RXQS);
|
|
|
|
mutex_unlock(&pf->avail_q_mutex);
|
|
|
|
|
2018-03-20 07:58:15 -07:00
|
|
|
if (pf->hw.func_caps.common_cap.rss_table_size)
|
|
|
|
set_bit(ICE_FLAG_RSS_ENA, pf->flags);
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
/* setup service timer and periodic service task */
|
|
|
|
timer_setup(&pf->serv_tmr, ice_service_timer, 0);
|
|
|
|
pf->serv_tmr_period = HZ;
|
|
|
|
INIT_WORK(&pf->serv_task, ice_service_task);
|
|
|
|
clear_bit(__ICE_SERVICE_SCHED, pf->state);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_ena_msix_range - Request a range of MSIX vectors from the OS
|
|
|
|
* @pf: board private structure
|
|
|
|
*
|
|
|
|
* compute the number of MSIX vectors required (v_budget) and request from
|
|
|
|
* the OS. Return the number of vectors reserved or negative on failure
|
|
|
|
*/
|
|
|
|
static int ice_ena_msix_range(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
int v_left, v_actual, v_budget = 0;
|
|
|
|
int needed, err, i;
|
|
|
|
|
|
|
|
v_left = pf->hw.func_caps.common_cap.num_msix_vectors;
|
|
|
|
|
|
|
|
/* reserve one vector for miscellaneous handler */
|
|
|
|
needed = 1;
|
|
|
|
v_budget += needed;
|
|
|
|
v_left -= needed;
|
|
|
|
|
|
|
|
/* reserve vectors for LAN traffic */
|
|
|
|
pf->num_lan_msix = min_t(int, num_online_cpus(), v_left);
|
|
|
|
v_budget += pf->num_lan_msix;
|
ice: Split irq_tracker into sw_irq_tracker and hw_irq_tracker
For the PF driver, when mapping interrupts to queues, we need to request
IRQs from the kernel and we also have to allocate interrupts from
the device.
Similarly, when the VF driver (iavf.ko) initializes, it requests the kernel
IRQs that it needs but it can't directly allocate interrupts in the device.
Instead, it sends a mailbox message to the ice driver, which then allocates
interrupts in the device on the VF driver's behalf.
Currently both these cases end up having to reserve entries in
pf->irq_tracker but irq_tracker itself is sized based on how many vectors
the PF driver needs. Under the right circumstances, the VF driver can fail
to get entries in irq_tracker, which will result in the VF driver failing
probe.
To fix this, sw_irq_tracker and hw_irq_tracker are introduced. The
sw_irq_tracker tracks only the PF's IRQ request and doesn't play any
role in VF init. hw_irq_tracker represents the device's interrupt space.
When interrupts have to be allocated in the device for either PF or VF,
hw_irq_tracker will be looked up to see if the device has run out of
interrupts.
Signed-off-by: Preethi Banala <preethi.banala@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-09-19 17:23:16 -07:00
|
|
|
v_left -= pf->num_lan_msix;
|
2018-03-20 07:58:10 -07:00
|
|
|
|
|
|
|
pf->msix_entries = devm_kcalloc(&pf->pdev->dev, v_budget,
|
2019-02-08 12:50:31 -08:00
|
|
|
sizeof(*pf->msix_entries), GFP_KERNEL);
|
2018-03-20 07:58:10 -07:00
|
|
|
|
|
|
|
if (!pf->msix_entries) {
|
|
|
|
err = -ENOMEM;
|
|
|
|
goto exit_err;
|
|
|
|
}
|
|
|
|
|
|
|
|
for (i = 0; i < v_budget; i++)
|
|
|
|
pf->msix_entries[i].entry = i;
|
|
|
|
|
|
|
|
/* actually reserve the vectors */
|
|
|
|
v_actual = pci_enable_msix_range(pf->pdev, pf->msix_entries,
|
|
|
|
ICE_MIN_MSIX, v_budget);
|
|
|
|
|
|
|
|
if (v_actual < 0) {
|
|
|
|
dev_err(&pf->pdev->dev, "unable to reserve MSI-X vectors\n");
|
|
|
|
err = v_actual;
|
|
|
|
goto msix_err;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (v_actual < v_budget) {
|
|
|
|
dev_warn(&pf->pdev->dev,
|
|
|
|
"not enough vectors. requested = %d, obtained = %d\n",
|
|
|
|
v_budget, v_actual);
|
|
|
|
if (v_actual >= (pf->num_lan_msix + 1)) {
|
ice: Split irq_tracker into sw_irq_tracker and hw_irq_tracker
For the PF driver, when mapping interrupts to queues, we need to request
IRQs from the kernel and we also have to allocate interrupts from
the device.
Similarly, when the VF driver (iavf.ko) initializes, it requests the kernel
IRQs that it needs but it can't directly allocate interrupts in the device.
Instead, it sends a mailbox message to the ice driver, which then allocates
interrupts in the device on the VF driver's behalf.
Currently both these cases end up having to reserve entries in
pf->irq_tracker but irq_tracker itself is sized based on how many vectors
the PF driver needs. Under the right circumstances, the VF driver can fail
to get entries in irq_tracker, which will result in the VF driver failing
probe.
To fix this, sw_irq_tracker and hw_irq_tracker are introduced. The
sw_irq_tracker tracks only the PF's IRQ request and doesn't play any
role in VF init. hw_irq_tracker represents the device's interrupt space.
When interrupts have to be allocated in the device for either PF or VF,
hw_irq_tracker will be looked up to see if the device has run out of
interrupts.
Signed-off-by: Preethi Banala <preethi.banala@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-09-19 17:23:16 -07:00
|
|
|
pf->num_avail_sw_msix = v_actual -
|
|
|
|
(pf->num_lan_msix + 1);
|
2018-03-20 07:58:10 -07:00
|
|
|
} else if (v_actual >= 2) {
|
|
|
|
pf->num_lan_msix = 1;
|
ice: Split irq_tracker into sw_irq_tracker and hw_irq_tracker
For the PF driver, when mapping interrupts to queues, we need to request
IRQs from the kernel and we also have to allocate interrupts from
the device.
Similarly, when the VF driver (iavf.ko) initializes, it requests the kernel
IRQs that it needs but it can't directly allocate interrupts in the device.
Instead, it sends a mailbox message to the ice driver, which then allocates
interrupts in the device on the VF driver's behalf.
Currently both these cases end up having to reserve entries in
pf->irq_tracker but irq_tracker itself is sized based on how many vectors
the PF driver needs. Under the right circumstances, the VF driver can fail
to get entries in irq_tracker, which will result in the VF driver failing
probe.
To fix this, sw_irq_tracker and hw_irq_tracker are introduced. The
sw_irq_tracker tracks only the PF's IRQ request and doesn't play any
role in VF init. hw_irq_tracker represents the device's interrupt space.
When interrupts have to be allocated in the device for either PF or VF,
hw_irq_tracker will be looked up to see if the device has run out of
interrupts.
Signed-off-by: Preethi Banala <preethi.banala@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-09-19 17:23:16 -07:00
|
|
|
pf->num_avail_sw_msix = v_actual - 2;
|
2018-03-20 07:58:10 -07:00
|
|
|
} else {
|
|
|
|
pci_disable_msix(pf->pdev);
|
|
|
|
err = -ERANGE;
|
|
|
|
goto msix_err;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return v_actual;
|
|
|
|
|
|
|
|
msix_err:
|
|
|
|
devm_kfree(&pf->pdev->dev, pf->msix_entries);
|
|
|
|
goto exit_err;
|
|
|
|
|
|
|
|
exit_err:
|
|
|
|
pf->num_lan_msix = 0;
|
|
|
|
clear_bit(ICE_FLAG_MSIX_ENA, pf->flags);
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_dis_msix - Disable MSI-X interrupt setup in OS
|
|
|
|
* @pf: board private structure
|
|
|
|
*/
|
|
|
|
static void ice_dis_msix(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
pci_disable_msix(pf->pdev);
|
|
|
|
devm_kfree(&pf->pdev->dev, pf->msix_entries);
|
|
|
|
pf->msix_entries = NULL;
|
|
|
|
clear_bit(ICE_FLAG_MSIX_ENA, pf->flags);
|
|
|
|
}
|
|
|
|
|
ice: Split irq_tracker into sw_irq_tracker and hw_irq_tracker
For the PF driver, when mapping interrupts to queues, we need to request
IRQs from the kernel and we also have to allocate interrupts from
the device.
Similarly, when the VF driver (iavf.ko) initializes, it requests the kernel
IRQs that it needs but it can't directly allocate interrupts in the device.
Instead, it sends a mailbox message to the ice driver, which then allocates
interrupts in the device on the VF driver's behalf.
Currently both these cases end up having to reserve entries in
pf->irq_tracker but irq_tracker itself is sized based on how many vectors
the PF driver needs. Under the right circumstances, the VF driver can fail
to get entries in irq_tracker, which will result in the VF driver failing
probe.
To fix this, sw_irq_tracker and hw_irq_tracker are introduced. The
sw_irq_tracker tracks only the PF's IRQ request and doesn't play any
role in VF init. hw_irq_tracker represents the device's interrupt space.
When interrupts have to be allocated in the device for either PF or VF,
hw_irq_tracker will be looked up to see if the device has run out of
interrupts.
Signed-off-by: Preethi Banala <preethi.banala@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-09-19 17:23:16 -07:00
|
|
|
/**
|
|
|
|
* ice_clear_interrupt_scheme - Undo things done by ice_init_interrupt_scheme
|
|
|
|
* @pf: board private structure
|
|
|
|
*/
|
|
|
|
static void ice_clear_interrupt_scheme(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
if (test_bit(ICE_FLAG_MSIX_ENA, pf->flags))
|
|
|
|
ice_dis_msix(pf);
|
|
|
|
|
ice: Refactor interrupt tracking
Currently we have two MSI-x (IRQ) trackers, one for OS requested MSI-x
entries (sw_irq_tracker) and one for hardware MSI-x vectors
(hw_irq_tracker). Generally the sw_irq_tracker has less entries than the
hw_irq_tracker because the hw_irq_tracker has entries equal to the max
allowed MSI-x per PF and the sw_irq_tracker is mainly the minimum (non
SR-IOV portion of the vectors, kernel granted IRQs). All of the non
SR-IOV portions of the driver (i.e. LAN queues, RDMA queues, OICR, etc.)
take at least one of each type of tracker resource. SR-IOV only grabs
entries from the hw_irq_tracker. There are a few issues with this approach
that can be seen when doing any kind of device reconfiguration (i.e.
ethtool -L, SR-IOV, etc.). One of them being, any time the driver creates
an ice_q_vector and associates it to a LAN queue pair it will grab and
use one entry from the hw_irq_tracker and one from the sw_irq_tracker.
If the indices on these does not match it will cause a Tx timeout, which
will cause a reset and then the indices will match up again and traffic
will resume. The mismatched indices come from the trackers not being the
same size and/or the search_hint in the two trackers not being equal.
Another reason for the refactor is the co-existence of features with
SR-IOV. If SR-IOV is enabled and the interrupts are taken from the end
of the sw_irq_tracker then other features can no longer use this space
because the hardware has now given the remaining interrupts to SR-IOV.
This patch reworks how we track MSI-x vectors by removing the
hw_irq_tracker completely and instead MSI-x resources needed for SR-IOV
are determined all at once instead of per VF. This can be done because
when creating VFs we know how many are wanted and how many MSI-x vectors
each VF needs. This also allows us to start using MSI-x resources from
the end of the PF's allowed MSI-x vectors so we are less likely to use
entries needed for other features (i.e. RDMA, L2 Offload, etc).
This patch also reworks the ice_res_tracker structure by removing the
search_hint and adding a new member - "end". Instead of having a
search_hint we will always search from 0. The new member, "end", will be
used to manipulate the end of the ice_res_tracker (specifically
sw_irq_tracker) during runtime based on MSI-x vectors needed by SR-IOV.
In the normal case, the end of ice_res_tracker will be equal to the
ice_res_tracker's num_entries.
The sriov_base_vector member was added to the PF structure. It is used
to represent the starting MSI-x index of all the needed MSI-x vectors
for all SR-IOV VFs. Depending on how many MSI-x are needed, SR-IOV may
have to take resources from the sw_irq_tracker. This is done by setting
the sw_irq_tracker->end equal to the pf->sriov_base_vector. When all
SR-IOV VFs are removed then the sw_irq_tracker->end is reset back to
sw_irq_tracker->num_entries. The sriov_base_vector, along with the VF's
number of MSI-x (pf->num_vf_msix), vf_id, and the base MSI-x index on
the PF (pf->hw.func_caps.common_cap.msix_vector_first_id), is used to
calculate the first HW absolute MSI-x index for each VF, which is used
to write to the VPINT_ALLOC[_PCI] and GLINT_VECT2FUNC registers to
program the VFs MSI-x PCI configuration bits. Also, the sriov_base_vector
is used along with VF's num_vf_msix, vf_id, and q_vector->v_idx to
determine the MSI-x register index (used for writing to GLINT_DYN_CTL)
within the PF's space.
Interrupt changes removed any references to hw_base_vector, hw_oicr_idx,
and hw_irq_tracker. Only sw_base_vector, sw_oicr_idx, and sw_irq_tracker
variables remain. Change all of these by removing the "sw_" prefix to
help avoid confusion with these variables and their use.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2019-04-16 10:30:44 -07:00
|
|
|
if (pf->irq_tracker) {
|
|
|
|
devm_kfree(&pf->pdev->dev, pf->irq_tracker);
|
|
|
|
pf->irq_tracker = NULL;
|
ice: Split irq_tracker into sw_irq_tracker and hw_irq_tracker
For the PF driver, when mapping interrupts to queues, we need to request
IRQs from the kernel and we also have to allocate interrupts from
the device.
Similarly, when the VF driver (iavf.ko) initializes, it requests the kernel
IRQs that it needs but it can't directly allocate interrupts in the device.
Instead, it sends a mailbox message to the ice driver, which then allocates
interrupts in the device on the VF driver's behalf.
Currently both these cases end up having to reserve entries in
pf->irq_tracker but irq_tracker itself is sized based on how many vectors
the PF driver needs. Under the right circumstances, the VF driver can fail
to get entries in irq_tracker, which will result in the VF driver failing
probe.
To fix this, sw_irq_tracker and hw_irq_tracker are introduced. The
sw_irq_tracker tracks only the PF's IRQ request and doesn't play any
role in VF init. hw_irq_tracker represents the device's interrupt space.
When interrupts have to be allocated in the device for either PF or VF,
hw_irq_tracker will be looked up to see if the device has run out of
interrupts.
Signed-off-by: Preethi Banala <preethi.banala@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-09-19 17:23:16 -07:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
/**
|
|
|
|
* ice_init_interrupt_scheme - Determine proper interrupt scheme
|
|
|
|
* @pf: board private structure to initialize
|
|
|
|
*/
|
|
|
|
static int ice_init_interrupt_scheme(struct ice_pf *pf)
|
|
|
|
{
|
ice: Refactor interrupt tracking
Currently we have two MSI-x (IRQ) trackers, one for OS requested MSI-x
entries (sw_irq_tracker) and one for hardware MSI-x vectors
(hw_irq_tracker). Generally the sw_irq_tracker has less entries than the
hw_irq_tracker because the hw_irq_tracker has entries equal to the max
allowed MSI-x per PF and the sw_irq_tracker is mainly the minimum (non
SR-IOV portion of the vectors, kernel granted IRQs). All of the non
SR-IOV portions of the driver (i.e. LAN queues, RDMA queues, OICR, etc.)
take at least one of each type of tracker resource. SR-IOV only grabs
entries from the hw_irq_tracker. There are a few issues with this approach
that can be seen when doing any kind of device reconfiguration (i.e.
ethtool -L, SR-IOV, etc.). One of them being, any time the driver creates
an ice_q_vector and associates it to a LAN queue pair it will grab and
use one entry from the hw_irq_tracker and one from the sw_irq_tracker.
If the indices on these does not match it will cause a Tx timeout, which
will cause a reset and then the indices will match up again and traffic
will resume. The mismatched indices come from the trackers not being the
same size and/or the search_hint in the two trackers not being equal.
Another reason for the refactor is the co-existence of features with
SR-IOV. If SR-IOV is enabled and the interrupts are taken from the end
of the sw_irq_tracker then other features can no longer use this space
because the hardware has now given the remaining interrupts to SR-IOV.
This patch reworks how we track MSI-x vectors by removing the
hw_irq_tracker completely and instead MSI-x resources needed for SR-IOV
are determined all at once instead of per VF. This can be done because
when creating VFs we know how many are wanted and how many MSI-x vectors
each VF needs. This also allows us to start using MSI-x resources from
the end of the PF's allowed MSI-x vectors so we are less likely to use
entries needed for other features (i.e. RDMA, L2 Offload, etc).
This patch also reworks the ice_res_tracker structure by removing the
search_hint and adding a new member - "end". Instead of having a
search_hint we will always search from 0. The new member, "end", will be
used to manipulate the end of the ice_res_tracker (specifically
sw_irq_tracker) during runtime based on MSI-x vectors needed by SR-IOV.
In the normal case, the end of ice_res_tracker will be equal to the
ice_res_tracker's num_entries.
The sriov_base_vector member was added to the PF structure. It is used
to represent the starting MSI-x index of all the needed MSI-x vectors
for all SR-IOV VFs. Depending on how many MSI-x are needed, SR-IOV may
have to take resources from the sw_irq_tracker. This is done by setting
the sw_irq_tracker->end equal to the pf->sriov_base_vector. When all
SR-IOV VFs are removed then the sw_irq_tracker->end is reset back to
sw_irq_tracker->num_entries. The sriov_base_vector, along with the VF's
number of MSI-x (pf->num_vf_msix), vf_id, and the base MSI-x index on
the PF (pf->hw.func_caps.common_cap.msix_vector_first_id), is used to
calculate the first HW absolute MSI-x index for each VF, which is used
to write to the VPINT_ALLOC[_PCI] and GLINT_VECT2FUNC registers to
program the VFs MSI-x PCI configuration bits. Also, the sriov_base_vector
is used along with VF's num_vf_msix, vf_id, and q_vector->v_idx to
determine the MSI-x register index (used for writing to GLINT_DYN_CTL)
within the PF's space.
Interrupt changes removed any references to hw_base_vector, hw_oicr_idx,
and hw_irq_tracker. Only sw_base_vector, sw_oicr_idx, and sw_irq_tracker
variables remain. Change all of these by removing the "sw_" prefix to
help avoid confusion with these variables and their use.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2019-04-16 10:30:44 -07:00
|
|
|
int vectors;
|
2018-03-20 07:58:10 -07:00
|
|
|
|
|
|
|
if (test_bit(ICE_FLAG_MSIX_ENA, pf->flags))
|
|
|
|
vectors = ice_ena_msix_range(pf);
|
|
|
|
else
|
|
|
|
return -ENODEV;
|
|
|
|
|
|
|
|
if (vectors < 0)
|
|
|
|
return vectors;
|
|
|
|
|
|
|
|
/* set up vector assignment tracking */
|
ice: Refactor interrupt tracking
Currently we have two MSI-x (IRQ) trackers, one for OS requested MSI-x
entries (sw_irq_tracker) and one for hardware MSI-x vectors
(hw_irq_tracker). Generally the sw_irq_tracker has less entries than the
hw_irq_tracker because the hw_irq_tracker has entries equal to the max
allowed MSI-x per PF and the sw_irq_tracker is mainly the minimum (non
SR-IOV portion of the vectors, kernel granted IRQs). All of the non
SR-IOV portions of the driver (i.e. LAN queues, RDMA queues, OICR, etc.)
take at least one of each type of tracker resource. SR-IOV only grabs
entries from the hw_irq_tracker. There are a few issues with this approach
that can be seen when doing any kind of device reconfiguration (i.e.
ethtool -L, SR-IOV, etc.). One of them being, any time the driver creates
an ice_q_vector and associates it to a LAN queue pair it will grab and
use one entry from the hw_irq_tracker and one from the sw_irq_tracker.
If the indices on these does not match it will cause a Tx timeout, which
will cause a reset and then the indices will match up again and traffic
will resume. The mismatched indices come from the trackers not being the
same size and/or the search_hint in the two trackers not being equal.
Another reason for the refactor is the co-existence of features with
SR-IOV. If SR-IOV is enabled and the interrupts are taken from the end
of the sw_irq_tracker then other features can no longer use this space
because the hardware has now given the remaining interrupts to SR-IOV.
This patch reworks how we track MSI-x vectors by removing the
hw_irq_tracker completely and instead MSI-x resources needed for SR-IOV
are determined all at once instead of per VF. This can be done because
when creating VFs we know how many are wanted and how many MSI-x vectors
each VF needs. This also allows us to start using MSI-x resources from
the end of the PF's allowed MSI-x vectors so we are less likely to use
entries needed for other features (i.e. RDMA, L2 Offload, etc).
This patch also reworks the ice_res_tracker structure by removing the
search_hint and adding a new member - "end". Instead of having a
search_hint we will always search from 0. The new member, "end", will be
used to manipulate the end of the ice_res_tracker (specifically
sw_irq_tracker) during runtime based on MSI-x vectors needed by SR-IOV.
In the normal case, the end of ice_res_tracker will be equal to the
ice_res_tracker's num_entries.
The sriov_base_vector member was added to the PF structure. It is used
to represent the starting MSI-x index of all the needed MSI-x vectors
for all SR-IOV VFs. Depending on how many MSI-x are needed, SR-IOV may
have to take resources from the sw_irq_tracker. This is done by setting
the sw_irq_tracker->end equal to the pf->sriov_base_vector. When all
SR-IOV VFs are removed then the sw_irq_tracker->end is reset back to
sw_irq_tracker->num_entries. The sriov_base_vector, along with the VF's
number of MSI-x (pf->num_vf_msix), vf_id, and the base MSI-x index on
the PF (pf->hw.func_caps.common_cap.msix_vector_first_id), is used to
calculate the first HW absolute MSI-x index for each VF, which is used
to write to the VPINT_ALLOC[_PCI] and GLINT_VECT2FUNC registers to
program the VFs MSI-x PCI configuration bits. Also, the sriov_base_vector
is used along with VF's num_vf_msix, vf_id, and q_vector->v_idx to
determine the MSI-x register index (used for writing to GLINT_DYN_CTL)
within the PF's space.
Interrupt changes removed any references to hw_base_vector, hw_oicr_idx,
and hw_irq_tracker. Only sw_base_vector, sw_oicr_idx, and sw_irq_tracker
variables remain. Change all of these by removing the "sw_" prefix to
help avoid confusion with these variables and their use.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2019-04-16 10:30:44 -07:00
|
|
|
pf->irq_tracker =
|
|
|
|
devm_kzalloc(&pf->pdev->dev, sizeof(*pf->irq_tracker) +
|
2019-02-08 12:50:31 -08:00
|
|
|
(sizeof(u16) * vectors), GFP_KERNEL);
|
ice: Refactor interrupt tracking
Currently we have two MSI-x (IRQ) trackers, one for OS requested MSI-x
entries (sw_irq_tracker) and one for hardware MSI-x vectors
(hw_irq_tracker). Generally the sw_irq_tracker has less entries than the
hw_irq_tracker because the hw_irq_tracker has entries equal to the max
allowed MSI-x per PF and the sw_irq_tracker is mainly the minimum (non
SR-IOV portion of the vectors, kernel granted IRQs). All of the non
SR-IOV portions of the driver (i.e. LAN queues, RDMA queues, OICR, etc.)
take at least one of each type of tracker resource. SR-IOV only grabs
entries from the hw_irq_tracker. There are a few issues with this approach
that can be seen when doing any kind of device reconfiguration (i.e.
ethtool -L, SR-IOV, etc.). One of them being, any time the driver creates
an ice_q_vector and associates it to a LAN queue pair it will grab and
use one entry from the hw_irq_tracker and one from the sw_irq_tracker.
If the indices on these does not match it will cause a Tx timeout, which
will cause a reset and then the indices will match up again and traffic
will resume. The mismatched indices come from the trackers not being the
same size and/or the search_hint in the two trackers not being equal.
Another reason for the refactor is the co-existence of features with
SR-IOV. If SR-IOV is enabled and the interrupts are taken from the end
of the sw_irq_tracker then other features can no longer use this space
because the hardware has now given the remaining interrupts to SR-IOV.
This patch reworks how we track MSI-x vectors by removing the
hw_irq_tracker completely and instead MSI-x resources needed for SR-IOV
are determined all at once instead of per VF. This can be done because
when creating VFs we know how many are wanted and how many MSI-x vectors
each VF needs. This also allows us to start using MSI-x resources from
the end of the PF's allowed MSI-x vectors so we are less likely to use
entries needed for other features (i.e. RDMA, L2 Offload, etc).
This patch also reworks the ice_res_tracker structure by removing the
search_hint and adding a new member - "end". Instead of having a
search_hint we will always search from 0. The new member, "end", will be
used to manipulate the end of the ice_res_tracker (specifically
sw_irq_tracker) during runtime based on MSI-x vectors needed by SR-IOV.
In the normal case, the end of ice_res_tracker will be equal to the
ice_res_tracker's num_entries.
The sriov_base_vector member was added to the PF structure. It is used
to represent the starting MSI-x index of all the needed MSI-x vectors
for all SR-IOV VFs. Depending on how many MSI-x are needed, SR-IOV may
have to take resources from the sw_irq_tracker. This is done by setting
the sw_irq_tracker->end equal to the pf->sriov_base_vector. When all
SR-IOV VFs are removed then the sw_irq_tracker->end is reset back to
sw_irq_tracker->num_entries. The sriov_base_vector, along with the VF's
number of MSI-x (pf->num_vf_msix), vf_id, and the base MSI-x index on
the PF (pf->hw.func_caps.common_cap.msix_vector_first_id), is used to
calculate the first HW absolute MSI-x index for each VF, which is used
to write to the VPINT_ALLOC[_PCI] and GLINT_VECT2FUNC registers to
program the VFs MSI-x PCI configuration bits. Also, the sriov_base_vector
is used along with VF's num_vf_msix, vf_id, and q_vector->v_idx to
determine the MSI-x register index (used for writing to GLINT_DYN_CTL)
within the PF's space.
Interrupt changes removed any references to hw_base_vector, hw_oicr_idx,
and hw_irq_tracker. Only sw_base_vector, sw_oicr_idx, and sw_irq_tracker
variables remain. Change all of these by removing the "sw_" prefix to
help avoid confusion with these variables and their use.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2019-04-16 10:30:44 -07:00
|
|
|
if (!pf->irq_tracker) {
|
2018-03-20 07:58:10 -07:00
|
|
|
ice_dis_msix(pf);
|
|
|
|
return -ENOMEM;
|
|
|
|
}
|
|
|
|
|
ice: Split irq_tracker into sw_irq_tracker and hw_irq_tracker
For the PF driver, when mapping interrupts to queues, we need to request
IRQs from the kernel and we also have to allocate interrupts from
the device.
Similarly, when the VF driver (iavf.ko) initializes, it requests the kernel
IRQs that it needs but it can't directly allocate interrupts in the device.
Instead, it sends a mailbox message to the ice driver, which then allocates
interrupts in the device on the VF driver's behalf.
Currently both these cases end up having to reserve entries in
pf->irq_tracker but irq_tracker itself is sized based on how many vectors
the PF driver needs. Under the right circumstances, the VF driver can fail
to get entries in irq_tracker, which will result in the VF driver failing
probe.
To fix this, sw_irq_tracker and hw_irq_tracker are introduced. The
sw_irq_tracker tracks only the PF's IRQ request and doesn't play any
role in VF init. hw_irq_tracker represents the device's interrupt space.
When interrupts have to be allocated in the device for either PF or VF,
hw_irq_tracker will be looked up to see if the device has run out of
interrupts.
Signed-off-by: Preethi Banala <preethi.banala@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-09-19 17:23:16 -07:00
|
|
|
/* populate SW interrupts pool with number of OS granted IRQs. */
|
|
|
|
pf->num_avail_sw_msix = vectors;
|
ice: Refactor interrupt tracking
Currently we have two MSI-x (IRQ) trackers, one for OS requested MSI-x
entries (sw_irq_tracker) and one for hardware MSI-x vectors
(hw_irq_tracker). Generally the sw_irq_tracker has less entries than the
hw_irq_tracker because the hw_irq_tracker has entries equal to the max
allowed MSI-x per PF and the sw_irq_tracker is mainly the minimum (non
SR-IOV portion of the vectors, kernel granted IRQs). All of the non
SR-IOV portions of the driver (i.e. LAN queues, RDMA queues, OICR, etc.)
take at least one of each type of tracker resource. SR-IOV only grabs
entries from the hw_irq_tracker. There are a few issues with this approach
that can be seen when doing any kind of device reconfiguration (i.e.
ethtool -L, SR-IOV, etc.). One of them being, any time the driver creates
an ice_q_vector and associates it to a LAN queue pair it will grab and
use one entry from the hw_irq_tracker and one from the sw_irq_tracker.
If the indices on these does not match it will cause a Tx timeout, which
will cause a reset and then the indices will match up again and traffic
will resume. The mismatched indices come from the trackers not being the
same size and/or the search_hint in the two trackers not being equal.
Another reason for the refactor is the co-existence of features with
SR-IOV. If SR-IOV is enabled and the interrupts are taken from the end
of the sw_irq_tracker then other features can no longer use this space
because the hardware has now given the remaining interrupts to SR-IOV.
This patch reworks how we track MSI-x vectors by removing the
hw_irq_tracker completely and instead MSI-x resources needed for SR-IOV
are determined all at once instead of per VF. This can be done because
when creating VFs we know how many are wanted and how many MSI-x vectors
each VF needs. This also allows us to start using MSI-x resources from
the end of the PF's allowed MSI-x vectors so we are less likely to use
entries needed for other features (i.e. RDMA, L2 Offload, etc).
This patch also reworks the ice_res_tracker structure by removing the
search_hint and adding a new member - "end". Instead of having a
search_hint we will always search from 0. The new member, "end", will be
used to manipulate the end of the ice_res_tracker (specifically
sw_irq_tracker) during runtime based on MSI-x vectors needed by SR-IOV.
In the normal case, the end of ice_res_tracker will be equal to the
ice_res_tracker's num_entries.
The sriov_base_vector member was added to the PF structure. It is used
to represent the starting MSI-x index of all the needed MSI-x vectors
for all SR-IOV VFs. Depending on how many MSI-x are needed, SR-IOV may
have to take resources from the sw_irq_tracker. This is done by setting
the sw_irq_tracker->end equal to the pf->sriov_base_vector. When all
SR-IOV VFs are removed then the sw_irq_tracker->end is reset back to
sw_irq_tracker->num_entries. The sriov_base_vector, along with the VF's
number of MSI-x (pf->num_vf_msix), vf_id, and the base MSI-x index on
the PF (pf->hw.func_caps.common_cap.msix_vector_first_id), is used to
calculate the first HW absolute MSI-x index for each VF, which is used
to write to the VPINT_ALLOC[_PCI] and GLINT_VECT2FUNC registers to
program the VFs MSI-x PCI configuration bits. Also, the sriov_base_vector
is used along with VF's num_vf_msix, vf_id, and q_vector->v_idx to
determine the MSI-x register index (used for writing to GLINT_DYN_CTL)
within the PF's space.
Interrupt changes removed any references to hw_base_vector, hw_oicr_idx,
and hw_irq_tracker. Only sw_base_vector, sw_oicr_idx, and sw_irq_tracker
variables remain. Change all of these by removing the "sw_" prefix to
help avoid confusion with these variables and their use.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2019-04-16 10:30:44 -07:00
|
|
|
pf->irq_tracker->num_entries = vectors;
|
|
|
|
pf->irq_tracker->end = pf->irq_tracker->num_entries;
|
ice: Split irq_tracker into sw_irq_tracker and hw_irq_tracker
For the PF driver, when mapping interrupts to queues, we need to request
IRQs from the kernel and we also have to allocate interrupts from
the device.
Similarly, when the VF driver (iavf.ko) initializes, it requests the kernel
IRQs that it needs but it can't directly allocate interrupts in the device.
Instead, it sends a mailbox message to the ice driver, which then allocates
interrupts in the device on the VF driver's behalf.
Currently both these cases end up having to reserve entries in
pf->irq_tracker but irq_tracker itself is sized based on how many vectors
the PF driver needs. Under the right circumstances, the VF driver can fail
to get entries in irq_tracker, which will result in the VF driver failing
probe.
To fix this, sw_irq_tracker and hw_irq_tracker are introduced. The
sw_irq_tracker tracks only the PF's IRQ request and doesn't play any
role in VF init. hw_irq_tracker represents the device's interrupt space.
When interrupts have to be allocated in the device for either PF or VF,
hw_irq_tracker will be looked up to see if the device has run out of
interrupts.
Signed-off-by: Preethi Banala <preethi.banala@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-09-19 17:23:16 -07:00
|
|
|
|
|
|
|
return 0;
|
2018-03-20 07:58:10 -07:00
|
|
|
}
|
|
|
|
|
ice: Fix tx_timeout in PF driver
Prior to this commit the driver was running into tx_timeouts when a
queue was stressed enough. This was happening because the HW tail
and SW tail (NTU) were incorrectly out of sync. Consequently this was
causing the HW head to collide with the HW tail, which to the hardware
means that all descriptors posted for Tx have been processed.
Due to the Tx logic used in the driver SW tail and HW tail are allowed
to be out of sync. This is done as an optimization because it allows the
driver to write HW tail as infrequently as possible, while still
updating the SW tail index to keep track. However, there are situations
where this results in the tail never getting updated, resulting in Tx
timeouts.
Tx HW tail write condition:
if (netif_xmit_stopped(txring_txq(tx_ring) || !skb->xmit_more)
writel(sw_tail, tx_ring->tail);
An issue was found in the Tx logic that was causing the afore mentioned
condition for updating HW tail to never happen, causing tx_timeouts.
In ice_xmit_frame_ring we calculate how many descriptors we need for the
Tx transaction based on the skb the kernel hands us. This is then passed
into ice_maybe_stop_tx along with some extra padding to determine if we
have enough descriptors available for this transaction. If we don't then
we return -EBUSY to the stack, otherwise we move on and eventually
prepare the Tx descriptors accordingly in ice_tx_map and set
next_to_watch. In ice_tx_map we make another call to ice_maybe_stop_tx
with a value of MAX_SKB_FRAGS + 4. The key here is that this value is
possibly less than the value we sent in the first call to
ice_maybe_stop_tx in ice_xmit_frame_ring. Now, if the number of unused
descriptors is between MAX_SKB_FRAGS + 4 and the value used in the first
call to ice_maybe_stop_tx in ice_xmit_frame_ring then we do not update
the HW tail because of the "Tx HW tail write condition" above. This is
because in ice_maybe_stop_tx we return success from ice_maybe_stop_tx
instead of calling __ice_maybe_stop_tx and subsequently calling
netif_stop_subqueue, which sets the __QUEUE_STATE_DEV_XOFF bit. This
bit is then checked in the "Tx HW tail write condition" by calling
netif_xmit_stopped and subsequently updating HW tail if the
afore mentioned bit is set.
In ice_clean_tx_irq, if next_to_watch is not NULL, we end up cleaning
the descriptors that HW sets the DD bit on and we have the budget. The
HW head will eventually run into the HW tail in response to the
description in the paragraph above.
The next time through ice_xmit_frame_ring we make the initial call to
ice_maybe_stop_tx with another skb from the stack. This time we do not
have enough descriptors available and we return NETDEV_TX_BUSY to the
stack and end up setting next_to_watch to NULL.
This is where we are stuck. In ice_clean_tx_irq we never clean anything
because next_to_watch is always NULL and in ice_xmit_frame_ring we never
update HW tail because we already return NETDEV_TX_BUSY to the stack and
eventually we hit a tx_timeout.
This issue was fixed by making sure that the second call to
ice_maybe_stop_tx in ice_tx_map is passed a value that is >= the value
that was used on the initial call to ice_maybe_stop_tx in
ice_xmit_frame_ring. This was done by adding the following defines to
make the logic more clear and to reduce the chance of mucking this up
again:
ICE_CACHE_LINE_BYTES 64
ICE_DESCS_PER_CACHE_LINE (ICE_CACHE_LINE_BYTES / \
sizeof(struct ice_tx_desc))
ICE_DESCS_FOR_CTX_DESC 1
ICE_DESCS_FOR_SKB_DATA_PTR 1
The ICE_CACHE_LINE_BYTES being 64 is an assumption being made so we
don't have to figure this out on every pass through the Tx path. Instead
I added a sanity check in ice_probe to verify cache line size and print
a message if it's not 64 Bytes. This will make it easier to file issues
if they are seen when the cache line size is not 64 Bytes when reading
from the GLPCI_CNF2 register.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-10-26 10:40:58 -07:00
|
|
|
/**
|
|
|
|
* ice_verify_cacheline_size - verify driver's assumption of 64 Byte cache lines
|
|
|
|
* @pf: pointer to the PF structure
|
|
|
|
*
|
|
|
|
* There is no error returned here because the driver should be able to handle
|
|
|
|
* 128 Byte cache lines, so we only print a warning in case issues are seen,
|
|
|
|
* specifically with Tx.
|
|
|
|
*/
|
|
|
|
static void ice_verify_cacheline_size(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
if (rd32(&pf->hw, GLPCI_CNF2) & GLPCI_CNF2_CACHELINE_SIZE_M)
|
|
|
|
dev_warn(&pf->pdev->dev,
|
|
|
|
"%d Byte cache line assumption is invalid, driver may have Tx timeouts!\n",
|
|
|
|
ICE_CACHE_LINE_BYTES);
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:05 -07:00
|
|
|
/**
|
|
|
|
* ice_probe - Device initialization routine
|
|
|
|
* @pdev: PCI device information struct
|
|
|
|
* @ent: entry in ice_pci_tbl
|
|
|
|
*
|
|
|
|
* Returns 0 on success, negative on failure
|
|
|
|
*/
|
2019-02-26 16:35:11 -08:00
|
|
|
static int
|
|
|
|
ice_probe(struct pci_dev *pdev, const struct pci_device_id __always_unused *ent)
|
2018-03-20 07:58:05 -07:00
|
|
|
{
|
2019-02-08 12:50:50 -08:00
|
|
|
struct device *dev = &pdev->dev;
|
2018-03-20 07:58:05 -07:00
|
|
|
struct ice_pf *pf;
|
|
|
|
struct ice_hw *hw;
|
|
|
|
int err;
|
|
|
|
|
|
|
|
/* this driver uses devres, see Documentation/driver-model/devres.txt */
|
|
|
|
err = pcim_enable_device(pdev);
|
|
|
|
if (err)
|
|
|
|
return err;
|
|
|
|
|
|
|
|
err = pcim_iomap_regions(pdev, BIT(ICE_BAR0), pci_name(pdev));
|
|
|
|
if (err) {
|
2019-02-08 12:50:50 -08:00
|
|
|
dev_err(dev, "BAR0 I/O map error %d\n", err);
|
2018-03-20 07:58:05 -07:00
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
2019-02-08 12:50:50 -08:00
|
|
|
pf = devm_kzalloc(dev, sizeof(*pf), GFP_KERNEL);
|
2018-03-20 07:58:05 -07:00
|
|
|
if (!pf)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
/* set up for high or low dma */
|
2019-02-08 12:50:50 -08:00
|
|
|
err = dma_set_mask_and_coherent(dev, DMA_BIT_MASK(64));
|
2018-03-20 07:58:05 -07:00
|
|
|
if (err)
|
2019-02-08 12:50:50 -08:00
|
|
|
err = dma_set_mask_and_coherent(dev, DMA_BIT_MASK(32));
|
2018-03-20 07:58:05 -07:00
|
|
|
if (err) {
|
2019-02-08 12:50:50 -08:00
|
|
|
dev_err(dev, "DMA configuration failed: 0x%x\n", err);
|
2018-03-20 07:58:05 -07:00
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
pci_enable_pcie_error_reporting(pdev);
|
|
|
|
pci_set_master(pdev);
|
|
|
|
|
|
|
|
pf->pdev = pdev;
|
|
|
|
pci_set_drvdata(pdev, pf);
|
|
|
|
set_bit(__ICE_DOWN, pf->state);
|
2018-08-09 06:29:57 -07:00
|
|
|
/* Disable service task until DOWN bit is cleared */
|
|
|
|
set_bit(__ICE_SERVICE_DIS, pf->state);
|
2018-03-20 07:58:05 -07:00
|
|
|
|
|
|
|
hw = &pf->hw;
|
|
|
|
hw->hw_addr = pcim_iomap_table(pdev)[ICE_BAR0];
|
|
|
|
hw->back = pf;
|
|
|
|
hw->vendor_id = pdev->vendor;
|
|
|
|
hw->device_id = pdev->device;
|
|
|
|
pci_read_config_byte(pdev, PCI_REVISION_ID, &hw->revision_id);
|
|
|
|
hw->subsystem_vendor_id = pdev->subsystem_vendor;
|
|
|
|
hw->subsystem_device_id = pdev->subsystem_device;
|
|
|
|
hw->bus.device = PCI_SLOT(pdev->devfn);
|
|
|
|
hw->bus.func = PCI_FUNC(pdev->devfn);
|
2018-03-20 07:58:07 -07:00
|
|
|
ice_set_ctrlq_len(hw);
|
|
|
|
|
2018-03-20 07:58:05 -07:00
|
|
|
pf->msg_enable = netif_msg_init(debug, ICE_DFLT_NETIF_M);
|
|
|
|
|
2018-03-20 07:58:06 -07:00
|
|
|
#ifndef CONFIG_DYNAMIC_DEBUG
|
|
|
|
if (debug < -1)
|
|
|
|
hw->debug_mask = debug;
|
|
|
|
#endif
|
|
|
|
|
2018-03-20 07:58:07 -07:00
|
|
|
err = ice_init_hw(hw);
|
|
|
|
if (err) {
|
2019-02-08 12:50:50 -08:00
|
|
|
dev_err(dev, "ice_init_hw failed: %d\n", err);
|
2018-03-20 07:58:07 -07:00
|
|
|
err = -EIO;
|
|
|
|
goto err_exit_unroll;
|
|
|
|
}
|
|
|
|
|
2019-02-08 12:50:50 -08:00
|
|
|
dev_info(dev, "firmware %d.%d.%05d api %d.%d\n",
|
2018-03-20 07:58:07 -07:00
|
|
|
hw->fw_maj_ver, hw->fw_min_ver, hw->fw_build,
|
|
|
|
hw->api_maj_ver, hw->api_min_ver);
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
ice_init_pf(pf);
|
|
|
|
|
2019-04-16 10:24:29 -07:00
|
|
|
err = ice_init_pf_dcb(pf, false);
|
2019-02-28 15:24:22 -08:00
|
|
|
if (err) {
|
|
|
|
clear_bit(ICE_FLAG_DCB_CAPABLE, pf->flags);
|
|
|
|
clear_bit(ICE_FLAG_DCB_ENA, pf->flags);
|
|
|
|
|
|
|
|
/* do not fail overall init if DCB init fails */
|
|
|
|
err = 0;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
ice_determine_q_usage(pf);
|
|
|
|
|
2018-10-26 10:41:03 -07:00
|
|
|
pf->num_alloc_vsi = hw->func_caps.guar_num_vsi;
|
2018-03-20 07:58:10 -07:00
|
|
|
if (!pf->num_alloc_vsi) {
|
|
|
|
err = -EIO;
|
|
|
|
goto err_init_pf_unroll;
|
|
|
|
}
|
|
|
|
|
2019-02-08 12:50:50 -08:00
|
|
|
pf->vsi = devm_kcalloc(dev, pf->num_alloc_vsi, sizeof(*pf->vsi),
|
|
|
|
GFP_KERNEL);
|
2018-03-20 07:58:10 -07:00
|
|
|
if (!pf->vsi) {
|
|
|
|
err = -ENOMEM;
|
|
|
|
goto err_init_pf_unroll;
|
|
|
|
}
|
|
|
|
|
|
|
|
err = ice_init_interrupt_scheme(pf);
|
|
|
|
if (err) {
|
2019-02-08 12:50:50 -08:00
|
|
|
dev_err(dev, "ice_init_interrupt_scheme failed: %d\n", err);
|
2018-03-20 07:58:10 -07:00
|
|
|
err = -EIO;
|
|
|
|
goto err_init_interrupt_unroll;
|
|
|
|
}
|
|
|
|
|
2018-08-09 06:29:57 -07:00
|
|
|
/* Driver is mostly up */
|
|
|
|
clear_bit(__ICE_DOWN, pf->state);
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
/* In case of MSIX we are going to setup the misc vector right here
|
|
|
|
* to handle admin queue events etc. In case of legacy and MSI
|
|
|
|
* the misc functionality and queue processing is combined in
|
|
|
|
* the same vector and that gets setup at open.
|
|
|
|
*/
|
|
|
|
if (test_bit(ICE_FLAG_MSIX_ENA, pf->flags)) {
|
|
|
|
err = ice_req_irq_msix_misc(pf);
|
|
|
|
if (err) {
|
2019-02-08 12:50:50 -08:00
|
|
|
dev_err(dev, "setup of misc vector failed: %d\n", err);
|
2018-03-20 07:58:10 -07:00
|
|
|
goto err_init_interrupt_unroll;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* create switch struct for the switch element created by FW on boot */
|
2019-02-08 12:50:50 -08:00
|
|
|
pf->first_sw = devm_kzalloc(dev, sizeof(*pf->first_sw), GFP_KERNEL);
|
2018-03-20 07:58:10 -07:00
|
|
|
if (!pf->first_sw) {
|
|
|
|
err = -ENOMEM;
|
|
|
|
goto err_msix_misc_unroll;
|
|
|
|
}
|
|
|
|
|
2018-08-09 06:29:54 -07:00
|
|
|
if (hw->evb_veb)
|
|
|
|
pf->first_sw->bridge_mode = BRIDGE_MODE_VEB;
|
|
|
|
else
|
|
|
|
pf->first_sw->bridge_mode = BRIDGE_MODE_VEPA;
|
|
|
|
|
2018-03-20 07:58:10 -07:00
|
|
|
pf->first_sw->pf = pf;
|
|
|
|
|
|
|
|
/* record the sw_id available for later use */
|
|
|
|
pf->first_sw->sw_id = hw->port_info->sw_id;
|
|
|
|
|
2018-03-20 07:58:11 -07:00
|
|
|
err = ice_setup_pf_sw(pf);
|
|
|
|
if (err) {
|
2019-02-08 12:50:50 -08:00
|
|
|
dev_err(dev, "probe failed due to setup pf switch:%d\n", err);
|
2018-03-20 07:58:11 -07:00
|
|
|
goto err_alloc_sw_unroll;
|
|
|
|
}
|
ice: Add support for switch filter programming
A VSI needs traffic directed towards it. This is done by programming
filter rules on the switch (embedded vSwitch) element in the hardware,
which connects the VSI to the ingress/egress port.
This patch introduces data structures and functions necessary to add
remove or update switch rules on the switch element. This is a pretty low
level function that is generic enough to add a whole range of filters.
This patch also introduces two top level functions ice_add_mac and
ice_remove mac which through a series of intermediate helper functions
eventually call ice_aq_sw_rules to add/delete simple MAC based filters.
It's worth noting that one invocation of ice_add_mac/ice_remove_mac
is capable of adding/deleting multiple MAC filters.
Also worth noting is the fact that the driver maintains a list of currently
active filters, so every filter addition/removal causes an update to this
list. This is done for a couple of reasons:
1) If two VSIs try to add the same filters, we need to detect it and do
things a little differently (i.e. use VSI lists, described below) as
the same filter can't be added more than once.
2) In the event of a hardware reset we can simply walk through this list
and restore the filters.
VSI Lists:
In a multi-VSI situation, it's possible that multiple VSIs want to add the
same filter rule. For example, two VSIs that want to receive broadcast
traffic would both add a filter for destination MAC ff:ff:ff:ff:ff:ff.
This can become cumbersome to maintain and so this is handled using a
VSI list.
A VSI list is resource that can be allocated in the hardware using the
ice_aq_alloc_free_res admin queue command. Simply put, a VSI list can
be thought of as a subscription list containing a set of VSIs to which
the packet should be forwarded, should the filter match.
For example, if VSI-0 has already added a broadcast filter, and VSI-1
wants to do the same thing, the filter creation flow will detect this,
allocate a VSI list and update the switch rule so that broadcast traffic
will now be forwarded to the VSI list which contains VSI-0 and VSI-1.
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:12 -07:00
|
|
|
|
2018-08-09 06:29:57 -07:00
|
|
|
clear_bit(__ICE_SERVICE_DIS, pf->state);
|
ice: Add support for switch filter programming
A VSI needs traffic directed towards it. This is done by programming
filter rules on the switch (embedded vSwitch) element in the hardware,
which connects the VSI to the ingress/egress port.
This patch introduces data structures and functions necessary to add
remove or update switch rules on the switch element. This is a pretty low
level function that is generic enough to add a whole range of filters.
This patch also introduces two top level functions ice_add_mac and
ice_remove mac which through a series of intermediate helper functions
eventually call ice_aq_sw_rules to add/delete simple MAC based filters.
It's worth noting that one invocation of ice_add_mac/ice_remove_mac
is capable of adding/deleting multiple MAC filters.
Also worth noting is the fact that the driver maintains a list of currently
active filters, so every filter addition/removal causes an update to this
list. This is done for a couple of reasons:
1) If two VSIs try to add the same filters, we need to detect it and do
things a little differently (i.e. use VSI lists, described below) as
the same filter can't be added more than once.
2) In the event of a hardware reset we can simply walk through this list
and restore the filters.
VSI Lists:
In a multi-VSI situation, it's possible that multiple VSIs want to add the
same filter rule. For example, two VSIs that want to receive broadcast
traffic would both add a filter for destination MAC ff:ff:ff:ff:ff:ff.
This can become cumbersome to maintain and so this is handled using a
VSI list.
A VSI list is resource that can be allocated in the hardware using the
ice_aq_alloc_free_res admin queue command. Simply put, a VSI list can
be thought of as a subscription list containing a set of VSIs to which
the packet should be forwarded, should the filter match.
For example, if VSI-0 has already added a broadcast filter, and VSI-1
wants to do the same thing, the filter creation flow will detect this,
allocate a VSI list and update the switch rule so that broadcast traffic
will now be forwarded to the VSI list which contains VSI-0 and VSI-1.
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:12 -07:00
|
|
|
|
|
|
|
/* since everything is good, start the service timer */
|
|
|
|
mod_timer(&pf->serv_tmr, round_jiffies(jiffies + pf->serv_tmr_period));
|
|
|
|
|
2019-02-26 16:35:23 -08:00
|
|
|
err = ice_init_link_events(pf->hw.port_info);
|
|
|
|
if (err) {
|
|
|
|
dev_err(dev, "ice_init_link_events failed: %d\n", err);
|
|
|
|
goto err_alloc_sw_unroll;
|
|
|
|
}
|
|
|
|
|
ice: Fix tx_timeout in PF driver
Prior to this commit the driver was running into tx_timeouts when a
queue was stressed enough. This was happening because the HW tail
and SW tail (NTU) were incorrectly out of sync. Consequently this was
causing the HW head to collide with the HW tail, which to the hardware
means that all descriptors posted for Tx have been processed.
Due to the Tx logic used in the driver SW tail and HW tail are allowed
to be out of sync. This is done as an optimization because it allows the
driver to write HW tail as infrequently as possible, while still
updating the SW tail index to keep track. However, there are situations
where this results in the tail never getting updated, resulting in Tx
timeouts.
Tx HW tail write condition:
if (netif_xmit_stopped(txring_txq(tx_ring) || !skb->xmit_more)
writel(sw_tail, tx_ring->tail);
An issue was found in the Tx logic that was causing the afore mentioned
condition for updating HW tail to never happen, causing tx_timeouts.
In ice_xmit_frame_ring we calculate how many descriptors we need for the
Tx transaction based on the skb the kernel hands us. This is then passed
into ice_maybe_stop_tx along with some extra padding to determine if we
have enough descriptors available for this transaction. If we don't then
we return -EBUSY to the stack, otherwise we move on and eventually
prepare the Tx descriptors accordingly in ice_tx_map and set
next_to_watch. In ice_tx_map we make another call to ice_maybe_stop_tx
with a value of MAX_SKB_FRAGS + 4. The key here is that this value is
possibly less than the value we sent in the first call to
ice_maybe_stop_tx in ice_xmit_frame_ring. Now, if the number of unused
descriptors is between MAX_SKB_FRAGS + 4 and the value used in the first
call to ice_maybe_stop_tx in ice_xmit_frame_ring then we do not update
the HW tail because of the "Tx HW tail write condition" above. This is
because in ice_maybe_stop_tx we return success from ice_maybe_stop_tx
instead of calling __ice_maybe_stop_tx and subsequently calling
netif_stop_subqueue, which sets the __QUEUE_STATE_DEV_XOFF bit. This
bit is then checked in the "Tx HW tail write condition" by calling
netif_xmit_stopped and subsequently updating HW tail if the
afore mentioned bit is set.
In ice_clean_tx_irq, if next_to_watch is not NULL, we end up cleaning
the descriptors that HW sets the DD bit on and we have the budget. The
HW head will eventually run into the HW tail in response to the
description in the paragraph above.
The next time through ice_xmit_frame_ring we make the initial call to
ice_maybe_stop_tx with another skb from the stack. This time we do not
have enough descriptors available and we return NETDEV_TX_BUSY to the
stack and end up setting next_to_watch to NULL.
This is where we are stuck. In ice_clean_tx_irq we never clean anything
because next_to_watch is always NULL and in ice_xmit_frame_ring we never
update HW tail because we already return NETDEV_TX_BUSY to the stack and
eventually we hit a tx_timeout.
This issue was fixed by making sure that the second call to
ice_maybe_stop_tx in ice_tx_map is passed a value that is >= the value
that was used on the initial call to ice_maybe_stop_tx in
ice_xmit_frame_ring. This was done by adding the following defines to
make the logic more clear and to reduce the chance of mucking this up
again:
ICE_CACHE_LINE_BYTES 64
ICE_DESCS_PER_CACHE_LINE (ICE_CACHE_LINE_BYTES / \
sizeof(struct ice_tx_desc))
ICE_DESCS_FOR_CTX_DESC 1
ICE_DESCS_FOR_SKB_DATA_PTR 1
The ICE_CACHE_LINE_BYTES being 64 is an assumption being made so we
don't have to figure this out on every pass through the Tx path. Instead
I added a sanity check in ice_probe to verify cache line size and print
a message if it's not 64 Bytes. This will make it easier to file issues
if they are seen when the cache line size is not 64 Bytes when reading
from the GLPCI_CNF2 register.
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-10-26 10:40:58 -07:00
|
|
|
ice_verify_cacheline_size(pf);
|
|
|
|
|
2018-03-20 07:58:05 -07:00
|
|
|
return 0;
|
2018-03-20 07:58:07 -07:00
|
|
|
|
2018-03-20 07:58:11 -07:00
|
|
|
err_alloc_sw_unroll:
|
2018-08-09 06:29:57 -07:00
|
|
|
set_bit(__ICE_SERVICE_DIS, pf->state);
|
2018-03-20 07:58:11 -07:00
|
|
|
set_bit(__ICE_DOWN, pf->state);
|
|
|
|
devm_kfree(&pf->pdev->dev, pf->first_sw);
|
2018-03-20 07:58:10 -07:00
|
|
|
err_msix_misc_unroll:
|
|
|
|
ice_free_irq_msix_misc(pf);
|
|
|
|
err_init_interrupt_unroll:
|
|
|
|
ice_clear_interrupt_scheme(pf);
|
2019-02-08 12:50:50 -08:00
|
|
|
devm_kfree(dev, pf->vsi);
|
2018-03-20 07:58:10 -07:00
|
|
|
err_init_pf_unroll:
|
|
|
|
ice_deinit_pf(pf);
|
|
|
|
ice_deinit_hw(hw);
|
2018-03-20 07:58:07 -07:00
|
|
|
err_exit_unroll:
|
|
|
|
pci_disable_pcie_error_reporting(pdev);
|
|
|
|
return err;
|
2018-03-20 07:58:05 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_remove - Device removal routine
|
|
|
|
* @pdev: PCI device information struct
|
|
|
|
*/
|
|
|
|
static void ice_remove(struct pci_dev *pdev)
|
|
|
|
{
|
|
|
|
struct ice_pf *pf = pci_get_drvdata(pdev);
|
2018-09-19 17:43:07 -07:00
|
|
|
int i;
|
2018-03-20 07:58:05 -07:00
|
|
|
|
|
|
|
if (!pf)
|
|
|
|
return;
|
|
|
|
|
2018-10-26 10:40:51 -07:00
|
|
|
for (i = 0; i < ICE_MAX_RESET_WAIT; i++) {
|
|
|
|
if (!ice_is_reset_in_progress(pf->state))
|
|
|
|
break;
|
|
|
|
msleep(100);
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:05 -07:00
|
|
|
set_bit(__ICE_DOWN, pf->state);
|
2018-08-09 06:29:57 -07:00
|
|
|
ice_service_task_stop(pf);
|
2018-03-20 07:58:07 -07:00
|
|
|
|
2018-09-19 17:42:55 -07:00
|
|
|
if (test_bit(ICE_FLAG_SRIOV_ENA, pf->flags))
|
|
|
|
ice_free_vfs(pf);
|
2018-08-09 06:29:50 -07:00
|
|
|
ice_vsi_release_all(pf);
|
2018-03-20 07:58:10 -07:00
|
|
|
ice_free_irq_msix_misc(pf);
|
2018-09-19 17:43:07 -07:00
|
|
|
ice_for_each_vsi(pf, i) {
|
|
|
|
if (!pf->vsi[i])
|
|
|
|
continue;
|
|
|
|
ice_vsi_free_q_vectors(pf->vsi[i]);
|
|
|
|
}
|
2018-03-20 07:58:10 -07:00
|
|
|
ice_clear_interrupt_scheme(pf);
|
|
|
|
ice_deinit_pf(pf);
|
2018-03-20 07:58:07 -07:00
|
|
|
ice_deinit_hw(&pf->hw);
|
2018-03-20 07:58:05 -07:00
|
|
|
pci_disable_pcie_error_reporting(pdev);
|
|
|
|
}
|
|
|
|
|
2019-02-13 10:51:15 -08:00
|
|
|
/**
|
|
|
|
* ice_pci_err_detected - warning that PCI error has been detected
|
|
|
|
* @pdev: PCI device information struct
|
|
|
|
* @err: the type of PCI error
|
|
|
|
*
|
|
|
|
* Called to warn that something happened on the PCI bus and the error handling
|
|
|
|
* is in progress. Allows the driver to gracefully prepare/handle PCI errors.
|
|
|
|
*/
|
|
|
|
static pci_ers_result_t
|
|
|
|
ice_pci_err_detected(struct pci_dev *pdev, enum pci_channel_state err)
|
|
|
|
{
|
|
|
|
struct ice_pf *pf = pci_get_drvdata(pdev);
|
|
|
|
|
|
|
|
if (!pf) {
|
|
|
|
dev_err(&pdev->dev, "%s: unrecoverable device error %d\n",
|
|
|
|
__func__, err);
|
|
|
|
return PCI_ERS_RESULT_DISCONNECT;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!test_bit(__ICE_SUSPENDED, pf->state)) {
|
|
|
|
ice_service_task_stop(pf);
|
|
|
|
|
|
|
|
if (!test_bit(__ICE_PREPARED_FOR_RESET, pf->state)) {
|
|
|
|
set_bit(__ICE_PFR_REQ, pf->state);
|
|
|
|
ice_prepare_for_reset(pf);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return PCI_ERS_RESULT_NEED_RESET;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_pci_err_slot_reset - a PCI slot reset has just happened
|
|
|
|
* @pdev: PCI device information struct
|
|
|
|
*
|
|
|
|
* Called to determine if the driver can recover from the PCI slot reset by
|
|
|
|
* using a register read to determine if the device is recoverable.
|
|
|
|
*/
|
|
|
|
static pci_ers_result_t ice_pci_err_slot_reset(struct pci_dev *pdev)
|
|
|
|
{
|
|
|
|
struct ice_pf *pf = pci_get_drvdata(pdev);
|
|
|
|
pci_ers_result_t result;
|
|
|
|
int err;
|
|
|
|
u32 reg;
|
|
|
|
|
|
|
|
err = pci_enable_device_mem(pdev);
|
|
|
|
if (err) {
|
|
|
|
dev_err(&pdev->dev,
|
|
|
|
"Cannot re-enable PCI device after reset, error %d\n",
|
|
|
|
err);
|
|
|
|
result = PCI_ERS_RESULT_DISCONNECT;
|
|
|
|
} else {
|
|
|
|
pci_set_master(pdev);
|
|
|
|
pci_restore_state(pdev);
|
|
|
|
pci_save_state(pdev);
|
|
|
|
pci_wake_from_d3(pdev, false);
|
|
|
|
|
|
|
|
/* Check for life */
|
|
|
|
reg = rd32(&pf->hw, GLGEN_RTRIG);
|
|
|
|
if (!reg)
|
|
|
|
result = PCI_ERS_RESULT_RECOVERED;
|
|
|
|
else
|
|
|
|
result = PCI_ERS_RESULT_DISCONNECT;
|
|
|
|
}
|
|
|
|
|
|
|
|
err = pci_cleanup_aer_uncorrect_error_status(pdev);
|
|
|
|
if (err)
|
|
|
|
dev_dbg(&pdev->dev,
|
|
|
|
"pci_cleanup_aer_uncorrect_error_status failed, error %d\n",
|
|
|
|
err);
|
|
|
|
/* non-fatal, continue */
|
|
|
|
|
|
|
|
return result;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_pci_err_resume - restart operations after PCI error recovery
|
|
|
|
* @pdev: PCI device information struct
|
|
|
|
*
|
|
|
|
* Called to allow the driver to bring things back up after PCI error and/or
|
|
|
|
* reset recovery have finished
|
|
|
|
*/
|
|
|
|
static void ice_pci_err_resume(struct pci_dev *pdev)
|
|
|
|
{
|
|
|
|
struct ice_pf *pf = pci_get_drvdata(pdev);
|
|
|
|
|
|
|
|
if (!pf) {
|
|
|
|
dev_err(&pdev->dev,
|
|
|
|
"%s failed, device is unrecoverable\n", __func__);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (test_bit(__ICE_SUSPENDED, pf->state)) {
|
|
|
|
dev_dbg(&pdev->dev, "%s failed to resume normal operations!\n",
|
|
|
|
__func__);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
ice_do_reset(pf, ICE_RESET_PFR);
|
|
|
|
ice_service_task_restart(pf);
|
|
|
|
mod_timer(&pf->serv_tmr, round_jiffies(jiffies + pf->serv_tmr_period));
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_pci_err_reset_prepare - prepare device driver for PCI reset
|
|
|
|
* @pdev: PCI device information struct
|
|
|
|
*/
|
|
|
|
static void ice_pci_err_reset_prepare(struct pci_dev *pdev)
|
|
|
|
{
|
|
|
|
struct ice_pf *pf = pci_get_drvdata(pdev);
|
|
|
|
|
|
|
|
if (!test_bit(__ICE_SUSPENDED, pf->state)) {
|
|
|
|
ice_service_task_stop(pf);
|
|
|
|
|
|
|
|
if (!test_bit(__ICE_PREPARED_FOR_RESET, pf->state)) {
|
|
|
|
set_bit(__ICE_PFR_REQ, pf->state);
|
|
|
|
ice_prepare_for_reset(pf);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_pci_err_reset_done - PCI reset done, device driver reset can begin
|
|
|
|
* @pdev: PCI device information struct
|
|
|
|
*/
|
|
|
|
static void ice_pci_err_reset_done(struct pci_dev *pdev)
|
|
|
|
{
|
|
|
|
ice_pci_err_resume(pdev);
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:05 -07:00
|
|
|
/* ice_pci_tbl - PCI Device ID Table
|
|
|
|
*
|
|
|
|
* Wildcard entries (PCI_ANY_ID) should come last
|
|
|
|
* Last entry must be all 0s
|
|
|
|
*
|
|
|
|
* { Vendor ID, Device ID, SubVendor ID, SubDevice ID,
|
|
|
|
* Class, Class Mask, private data (not used) }
|
|
|
|
*/
|
|
|
|
static const struct pci_device_id ice_pci_tbl[] = {
|
2018-10-18 08:37:04 -07:00
|
|
|
{ PCI_VDEVICE(INTEL, ICE_DEV_ID_E810C_BACKPLANE), 0 },
|
|
|
|
{ PCI_VDEVICE(INTEL, ICE_DEV_ID_E810C_QSFP), 0 },
|
|
|
|
{ PCI_VDEVICE(INTEL, ICE_DEV_ID_E810C_SFP), 0 },
|
2018-03-20 07:58:05 -07:00
|
|
|
/* required last entry */
|
|
|
|
{ 0, }
|
|
|
|
};
|
|
|
|
MODULE_DEVICE_TABLE(pci, ice_pci_tbl);
|
|
|
|
|
2019-02-13 10:51:15 -08:00
|
|
|
static const struct pci_error_handlers ice_pci_err_handler = {
|
|
|
|
.error_detected = ice_pci_err_detected,
|
|
|
|
.slot_reset = ice_pci_err_slot_reset,
|
|
|
|
.reset_prepare = ice_pci_err_reset_prepare,
|
|
|
|
.reset_done = ice_pci_err_reset_done,
|
|
|
|
.resume = ice_pci_err_resume
|
|
|
|
};
|
|
|
|
|
2018-03-20 07:58:05 -07:00
|
|
|
static struct pci_driver ice_driver = {
|
|
|
|
.name = KBUILD_MODNAME,
|
|
|
|
.id_table = ice_pci_tbl,
|
|
|
|
.probe = ice_probe,
|
|
|
|
.remove = ice_remove,
|
2018-09-19 17:42:55 -07:00
|
|
|
.sriov_configure = ice_sriov_configure,
|
2019-02-13 10:51:15 -08:00
|
|
|
.err_handler = &ice_pci_err_handler
|
2018-03-20 07:58:05 -07:00
|
|
|
};
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_module_init - Driver registration routine
|
|
|
|
*
|
|
|
|
* ice_module_init is the first routine called when the driver is
|
|
|
|
* loaded. All it does is register with the PCI subsystem.
|
|
|
|
*/
|
|
|
|
static int __init ice_module_init(void)
|
|
|
|
{
|
|
|
|
int status;
|
|
|
|
|
|
|
|
pr_info("%s - version %s\n", ice_driver_string, ice_drv_ver);
|
|
|
|
pr_info("%s\n", ice_copyright);
|
|
|
|
|
2018-08-09 06:29:50 -07:00
|
|
|
ice_wq = alloc_workqueue("%s", WQ_MEM_RECLAIM, 0, KBUILD_MODNAME);
|
2018-03-20 07:58:10 -07:00
|
|
|
if (!ice_wq) {
|
|
|
|
pr_err("Failed to create workqueue\n");
|
|
|
|
return -ENOMEM;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:05 -07:00
|
|
|
status = pci_register_driver(&ice_driver);
|
2018-03-20 07:58:10 -07:00
|
|
|
if (status) {
|
2018-03-20 07:58:05 -07:00
|
|
|
pr_err("failed to register pci driver, err %d\n", status);
|
2018-03-20 07:58:10 -07:00
|
|
|
destroy_workqueue(ice_wq);
|
|
|
|
}
|
2018-03-20 07:58:05 -07:00
|
|
|
|
|
|
|
return status;
|
|
|
|
}
|
|
|
|
module_init(ice_module_init);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_module_exit - Driver exit cleanup routine
|
|
|
|
*
|
|
|
|
* ice_module_exit is called just before the driver is removed
|
|
|
|
* from memory.
|
|
|
|
*/
|
|
|
|
static void __exit ice_module_exit(void)
|
|
|
|
{
|
|
|
|
pci_unregister_driver(&ice_driver);
|
2018-03-20 07:58:10 -07:00
|
|
|
destroy_workqueue(ice_wq);
|
2018-03-20 07:58:05 -07:00
|
|
|
pr_info("module unloaded\n");
|
|
|
|
}
|
|
|
|
module_exit(ice_module_exit);
|
2018-03-20 07:58:11 -07:00
|
|
|
|
2018-03-20 07:58:19 -07:00
|
|
|
/**
|
2019-02-19 15:04:13 -08:00
|
|
|
* ice_set_mac_address - NDO callback to set MAC address
|
2018-03-20 07:58:19 -07:00
|
|
|
* @netdev: network interface device structure
|
|
|
|
* @pi: pointer to an address structure
|
|
|
|
*
|
|
|
|
* Returns 0 on success, negative on failure
|
|
|
|
*/
|
|
|
|
static int ice_set_mac_address(struct net_device *netdev, void *pi)
|
|
|
|
{
|
|
|
|
struct ice_netdev_priv *np = netdev_priv(netdev);
|
|
|
|
struct ice_vsi *vsi = np->vsi;
|
|
|
|
struct ice_pf *pf = vsi->back;
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
struct sockaddr *addr = pi;
|
|
|
|
enum ice_status status;
|
|
|
|
LIST_HEAD(a_mac_list);
|
|
|
|
LIST_HEAD(r_mac_list);
|
|
|
|
u8 flags = 0;
|
|
|
|
int err;
|
|
|
|
u8 *mac;
|
|
|
|
|
|
|
|
mac = (u8 *)addr->sa_data;
|
|
|
|
|
|
|
|
if (!is_valid_ether_addr(mac))
|
|
|
|
return -EADDRNOTAVAIL;
|
|
|
|
|
|
|
|
if (ether_addr_equal(netdev->dev_addr, mac)) {
|
|
|
|
netdev_warn(netdev, "already using mac %pM\n", mac);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (test_bit(__ICE_DOWN, pf->state) ||
|
2018-09-19 17:23:11 -07:00
|
|
|
ice_is_reset_in_progress(pf->state)) {
|
2018-03-20 07:58:19 -07:00
|
|
|
netdev_err(netdev, "can't set mac %pM. device not ready\n",
|
|
|
|
mac);
|
|
|
|
return -EBUSY;
|
|
|
|
}
|
|
|
|
|
2019-02-19 15:04:13 -08:00
|
|
|
/* When we change the MAC address we also have to change the MAC address
|
|
|
|
* based filter rules that were created previously for the old MAC
|
2018-03-20 07:58:19 -07:00
|
|
|
* address. So first, we remove the old filter rule using ice_remove_mac
|
|
|
|
* and then create a new filter rule using ice_add_mac. Note that for
|
2019-02-19 15:04:13 -08:00
|
|
|
* both these operations, we first need to form a "list" of MAC
|
|
|
|
* addresses (even though in this case, we have only 1 MAC address to be
|
2018-03-20 07:58:19 -07:00
|
|
|
* added/removed) and this done using ice_add_mac_to_list. Depending on
|
2019-02-19 15:04:13 -08:00
|
|
|
* the ensuing operation this "list" of MAC addresses is either to be
|
2018-03-20 07:58:19 -07:00
|
|
|
* added or removed from the filter.
|
|
|
|
*/
|
|
|
|
err = ice_add_mac_to_list(vsi, &r_mac_list, netdev->dev_addr);
|
|
|
|
if (err) {
|
|
|
|
err = -EADDRNOTAVAIL;
|
|
|
|
goto free_lists;
|
|
|
|
}
|
|
|
|
|
|
|
|
status = ice_remove_mac(hw, &r_mac_list);
|
|
|
|
if (status) {
|
|
|
|
err = -EADDRNOTAVAIL;
|
|
|
|
goto free_lists;
|
|
|
|
}
|
|
|
|
|
|
|
|
err = ice_add_mac_to_list(vsi, &a_mac_list, mac);
|
|
|
|
if (err) {
|
|
|
|
err = -EADDRNOTAVAIL;
|
|
|
|
goto free_lists;
|
|
|
|
}
|
|
|
|
|
|
|
|
status = ice_add_mac(hw, &a_mac_list);
|
|
|
|
if (status) {
|
|
|
|
err = -EADDRNOTAVAIL;
|
|
|
|
goto free_lists;
|
|
|
|
}
|
|
|
|
|
|
|
|
free_lists:
|
|
|
|
/* free list entries */
|
|
|
|
ice_free_fltr_list(&pf->pdev->dev, &r_mac_list);
|
|
|
|
ice_free_fltr_list(&pf->pdev->dev, &a_mac_list);
|
|
|
|
|
|
|
|
if (err) {
|
|
|
|
netdev_err(netdev, "can't set mac %pM. filter update failed\n",
|
|
|
|
mac);
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
2019-02-19 15:04:13 -08:00
|
|
|
/* change the netdev's MAC address */
|
2018-03-20 07:58:19 -07:00
|
|
|
memcpy(netdev->dev_addr, mac, netdev->addr_len);
|
|
|
|
netdev_dbg(vsi->netdev, "updated mac address to %pM\n",
|
|
|
|
netdev->dev_addr);
|
|
|
|
|
2019-02-19 15:04:13 -08:00
|
|
|
/* write new MAC address to the firmware */
|
2018-03-20 07:58:19 -07:00
|
|
|
flags = ICE_AQC_MAN_MAC_UPDATE_LAA_WOL;
|
|
|
|
status = ice_aq_manage_mac_write(hw, mac, flags, NULL);
|
|
|
|
if (status) {
|
|
|
|
netdev_err(netdev, "can't set mac %pM. write to firmware failed.\n",
|
|
|
|
mac);
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_set_rx_mode - NDO callback to set the netdev filters
|
|
|
|
* @netdev: network interface device structure
|
|
|
|
*/
|
|
|
|
static void ice_set_rx_mode(struct net_device *netdev)
|
|
|
|
{
|
|
|
|
struct ice_netdev_priv *np = netdev_priv(netdev);
|
|
|
|
struct ice_vsi *vsi = np->vsi;
|
|
|
|
|
|
|
|
if (!vsi)
|
|
|
|
return;
|
|
|
|
|
|
|
|
/* Set the flags to synchronize filters
|
|
|
|
* ndo_set_rx_mode may be triggered even without a change in netdev
|
|
|
|
* flags
|
|
|
|
*/
|
|
|
|
set_bit(ICE_VSI_FLAG_UMAC_FLTR_CHANGED, vsi->flags);
|
|
|
|
set_bit(ICE_VSI_FLAG_MMAC_FLTR_CHANGED, vsi->flags);
|
|
|
|
set_bit(ICE_FLAG_FLTR_SYNC, vsi->back->flags);
|
|
|
|
|
|
|
|
/* schedule our worker thread which will take care of
|
|
|
|
* applying the new filter changes
|
|
|
|
*/
|
|
|
|
ice_service_task_schedule(vsi->back);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_fdb_add - add an entry to the hardware database
|
|
|
|
* @ndm: the input from the stack
|
|
|
|
* @tb: pointer to array of nladdr (unused)
|
|
|
|
* @dev: the net device pointer
|
|
|
|
* @addr: the MAC address entry being added
|
2019-02-19 15:04:13 -08:00
|
|
|
* @vid: VLAN ID
|
2018-03-20 07:58:19 -07:00
|
|
|
* @flags: instructions from stack about fdb operation
|
2019-02-08 12:50:28 -08:00
|
|
|
* @extack: netlink extended ack
|
2018-03-20 07:58:19 -07:00
|
|
|
*/
|
2019-02-08 12:50:28 -08:00
|
|
|
static int
|
|
|
|
ice_fdb_add(struct ndmsg *ndm, struct nlattr __always_unused *tb[],
|
|
|
|
struct net_device *dev, const unsigned char *addr, u16 vid,
|
|
|
|
u16 flags, struct netlink_ext_ack __always_unused *extack)
|
2018-03-20 07:58:19 -07:00
|
|
|
{
|
|
|
|
int err;
|
|
|
|
|
|
|
|
if (vid) {
|
|
|
|
netdev_err(dev, "VLANs aren't supported yet for dev_uc|mc_add()\n");
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
if (ndm->ndm_state && !(ndm->ndm_state & NUD_PERMANENT)) {
|
|
|
|
netdev_err(dev, "FDB only supports static addresses\n");
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (is_unicast_ether_addr(addr) || is_link_local_ether_addr(addr))
|
|
|
|
err = dev_uc_add_excl(dev, addr);
|
|
|
|
else if (is_multicast_ether_addr(addr))
|
|
|
|
err = dev_mc_add_excl(dev, addr);
|
|
|
|
else
|
|
|
|
err = -EINVAL;
|
|
|
|
|
|
|
|
/* Only return duplicate errors if NLM_F_EXCL is set */
|
|
|
|
if (err == -EEXIST && !(flags & NLM_F_EXCL))
|
|
|
|
err = 0;
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_fdb_del - delete an entry from the hardware database
|
|
|
|
* @ndm: the input from the stack
|
|
|
|
* @tb: pointer to array of nladdr (unused)
|
|
|
|
* @dev: the net device pointer
|
|
|
|
* @addr: the MAC address entry being added
|
2019-02-19 15:04:13 -08:00
|
|
|
* @vid: VLAN ID
|
2018-03-20 07:58:19 -07:00
|
|
|
*/
|
2019-02-26 16:35:11 -08:00
|
|
|
static int
|
|
|
|
ice_fdb_del(struct ndmsg *ndm, __always_unused struct nlattr *tb[],
|
|
|
|
struct net_device *dev, const unsigned char *addr,
|
|
|
|
__always_unused u16 vid)
|
2018-03-20 07:58:19 -07:00
|
|
|
{
|
|
|
|
int err;
|
|
|
|
|
|
|
|
if (ndm->ndm_state & NUD_PERMANENT) {
|
|
|
|
netdev_err(dev, "FDB only supports static addresses\n");
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (is_unicast_ether_addr(addr))
|
|
|
|
err = dev_uc_del(dev, addr);
|
|
|
|
else if (is_multicast_ether_addr(addr))
|
|
|
|
err = dev_mc_del(dev, addr);
|
|
|
|
else
|
|
|
|
err = -EINVAL;
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:15 -07:00
|
|
|
/**
|
|
|
|
* ice_set_features - set the netdev feature flags
|
|
|
|
* @netdev: ptr to the netdev being adjusted
|
|
|
|
* @features: the feature set that the stack is suggesting
|
|
|
|
*/
|
2019-02-26 16:35:11 -08:00
|
|
|
static int
|
|
|
|
ice_set_features(struct net_device *netdev, netdev_features_t features)
|
2018-03-20 07:58:15 -07:00
|
|
|
{
|
|
|
|
struct ice_netdev_priv *np = netdev_priv(netdev);
|
|
|
|
struct ice_vsi *vsi = np->vsi;
|
|
|
|
int ret = 0;
|
|
|
|
|
2019-04-16 10:21:23 -07:00
|
|
|
/* Multiple features can be changed in one call so keep features in
|
|
|
|
* separate if/else statements to guarantee each feature is checked
|
|
|
|
*/
|
2018-09-19 17:23:17 -07:00
|
|
|
if (features & NETIF_F_RXHASH && !(netdev->features & NETIF_F_RXHASH))
|
|
|
|
ret = ice_vsi_manage_rss_lut(vsi, true);
|
|
|
|
else if (!(features & NETIF_F_RXHASH) &&
|
|
|
|
netdev->features & NETIF_F_RXHASH)
|
|
|
|
ret = ice_vsi_manage_rss_lut(vsi, false);
|
|
|
|
|
2018-03-20 07:58:15 -07:00
|
|
|
if ((features & NETIF_F_HW_VLAN_CTAG_RX) &&
|
|
|
|
!(netdev->features & NETIF_F_HW_VLAN_CTAG_RX))
|
|
|
|
ret = ice_vsi_manage_vlan_stripping(vsi, true);
|
|
|
|
else if (!(features & NETIF_F_HW_VLAN_CTAG_RX) &&
|
|
|
|
(netdev->features & NETIF_F_HW_VLAN_CTAG_RX))
|
|
|
|
ret = ice_vsi_manage_vlan_stripping(vsi, false);
|
2019-04-16 10:21:23 -07:00
|
|
|
|
|
|
|
if ((features & NETIF_F_HW_VLAN_CTAG_TX) &&
|
|
|
|
!(netdev->features & NETIF_F_HW_VLAN_CTAG_TX))
|
2018-03-20 07:58:15 -07:00
|
|
|
ret = ice_vsi_manage_vlan_insertion(vsi);
|
|
|
|
else if (!(features & NETIF_F_HW_VLAN_CTAG_TX) &&
|
|
|
|
(netdev->features & NETIF_F_HW_VLAN_CTAG_TX))
|
|
|
|
ret = ice_vsi_manage_vlan_insertion(vsi);
|
|
|
|
|
2019-04-16 10:30:39 -07:00
|
|
|
if ((features & NETIF_F_HW_VLAN_CTAG_FILTER) &&
|
|
|
|
!(netdev->features & NETIF_F_HW_VLAN_CTAG_FILTER))
|
|
|
|
ret = ice_cfg_vlan_pruning(vsi, true, false);
|
|
|
|
else if (!(features & NETIF_F_HW_VLAN_CTAG_FILTER) &&
|
|
|
|
(netdev->features & NETIF_F_HW_VLAN_CTAG_FILTER))
|
|
|
|
ret = ice_cfg_vlan_pruning(vsi, false, false);
|
|
|
|
|
2018-03-20 07:58:15 -07:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2019-02-19 15:04:13 -08:00
|
|
|
* ice_vsi_vlan_setup - Setup VLAN offload properties on a VSI
|
|
|
|
* @vsi: VSI to setup VLAN properties for
|
2018-03-20 07:58:15 -07:00
|
|
|
*/
|
|
|
|
static int ice_vsi_vlan_setup(struct ice_vsi *vsi)
|
|
|
|
{
|
|
|
|
int ret = 0;
|
|
|
|
|
|
|
|
if (vsi->netdev->features & NETIF_F_HW_VLAN_CTAG_RX)
|
|
|
|
ret = ice_vsi_manage_vlan_stripping(vsi, true);
|
|
|
|
if (vsi->netdev->features & NETIF_F_HW_VLAN_CTAG_TX)
|
|
|
|
ret = ice_vsi_manage_vlan_insertion(vsi);
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:13 -07:00
|
|
|
/**
|
|
|
|
* ice_vsi_cfg - Setup the VSI
|
|
|
|
* @vsi: the VSI being configured
|
|
|
|
*
|
|
|
|
* Return 0 on success and negative value on error
|
|
|
|
*/
|
2019-04-16 10:30:43 -07:00
|
|
|
int ice_vsi_cfg(struct ice_vsi *vsi)
|
2018-03-20 07:58:13 -07:00
|
|
|
{
|
|
|
|
int err;
|
|
|
|
|
2018-08-09 06:29:00 -07:00
|
|
|
if (vsi->netdev) {
|
|
|
|
ice_set_rx_mode(vsi->netdev);
|
2018-10-26 10:40:54 -07:00
|
|
|
|
|
|
|
err = ice_vsi_vlan_setup(vsi);
|
|
|
|
|
2018-08-09 06:29:00 -07:00
|
|
|
if (err)
|
|
|
|
return err;
|
|
|
|
}
|
2019-02-28 15:24:27 -08:00
|
|
|
ice_vsi_cfg_dcb_rings(vsi);
|
2018-12-19 10:03:27 -08:00
|
|
|
|
|
|
|
err = ice_vsi_cfg_lan_txqs(vsi);
|
2018-03-20 07:58:13 -07:00
|
|
|
if (!err)
|
|
|
|
err = ice_vsi_cfg_rxqs(vsi);
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:14 -07:00
|
|
|
/**
|
|
|
|
* ice_napi_enable_all - Enable NAPI for all q_vectors in the VSI
|
|
|
|
* @vsi: the VSI being configured
|
|
|
|
*/
|
|
|
|
static void ice_napi_enable_all(struct ice_vsi *vsi)
|
|
|
|
{
|
|
|
|
int q_idx;
|
|
|
|
|
|
|
|
if (!vsi->netdev)
|
|
|
|
return;
|
|
|
|
|
2019-04-16 10:21:28 -07:00
|
|
|
ice_for_each_q_vector(vsi, q_idx) {
|
2018-11-29 01:54:10 +00:00
|
|
|
struct ice_q_vector *q_vector = vsi->q_vectors[q_idx];
|
|
|
|
|
|
|
|
if (q_vector->rx.ring || q_vector->tx.ring)
|
|
|
|
napi_enable(&q_vector->napi);
|
|
|
|
}
|
2018-03-20 07:58:14 -07:00
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:13 -07:00
|
|
|
/**
|
|
|
|
* ice_up_complete - Finish the last steps of bringing up a connection
|
|
|
|
* @vsi: The VSI being configured
|
|
|
|
*
|
|
|
|
* Return 0 on success and negative value on error
|
|
|
|
*/
|
|
|
|
static int ice_up_complete(struct ice_vsi *vsi)
|
|
|
|
{
|
|
|
|
struct ice_pf *pf = vsi->back;
|
|
|
|
int err;
|
|
|
|
|
|
|
|
if (test_bit(ICE_FLAG_MSIX_ENA, pf->flags))
|
|
|
|
ice_vsi_cfg_msix(vsi);
|
|
|
|
else
|
|
|
|
return -ENOTSUPP;
|
|
|
|
|
|
|
|
/* Enable only Rx rings, Tx rings were enabled by the FW when the
|
|
|
|
* Tx queue group list was configured and the context bits were
|
|
|
|
* programmed using ice_vsi_cfg_txqs
|
|
|
|
*/
|
|
|
|
err = ice_vsi_start_rx_rings(vsi);
|
|
|
|
if (err)
|
|
|
|
return err;
|
|
|
|
|
|
|
|
clear_bit(__ICE_DOWN, vsi->state);
|
2018-03-20 07:58:14 -07:00
|
|
|
ice_napi_enable_all(vsi);
|
2018-03-20 07:58:13 -07:00
|
|
|
ice_vsi_ena_irq(vsi);
|
|
|
|
|
|
|
|
if (vsi->port_info &&
|
|
|
|
(vsi->port_info->phy.link_info.link_info & ICE_AQ_LINK_UP) &&
|
|
|
|
vsi->netdev) {
|
|
|
|
ice_print_link_msg(vsi, true);
|
|
|
|
netif_tx_start_all_queues(vsi->netdev);
|
|
|
|
netif_carrier_on(vsi->netdev);
|
|
|
|
}
|
|
|
|
|
|
|
|
ice_service_task_schedule(pf);
|
|
|
|
|
2019-02-26 16:35:07 -08:00
|
|
|
return 0;
|
2018-03-20 07:58:13 -07:00
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:16 -07:00
|
|
|
/**
|
|
|
|
* ice_up - Bring the connection back up after being down
|
|
|
|
* @vsi: VSI being configured
|
|
|
|
*/
|
|
|
|
int ice_up(struct ice_vsi *vsi)
|
|
|
|
{
|
|
|
|
int err;
|
|
|
|
|
|
|
|
err = ice_vsi_cfg(vsi);
|
|
|
|
if (!err)
|
|
|
|
err = ice_up_complete(vsi);
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_fetch_u64_stats_per_ring - get packets and bytes stats per ring
|
|
|
|
* @ring: Tx or Rx ring to read stats from
|
|
|
|
* @pkts: packets stats counter
|
|
|
|
* @bytes: bytes stats counter
|
|
|
|
*
|
|
|
|
* This function fetches stats from the ring considering the atomic operations
|
|
|
|
* that needs to be performed to read u64 values in 32 bit machine.
|
|
|
|
*/
|
2019-02-26 16:35:11 -08:00
|
|
|
static void
|
|
|
|
ice_fetch_u64_stats_per_ring(struct ice_ring *ring, u64 *pkts, u64 *bytes)
|
2018-03-20 07:58:16 -07:00
|
|
|
{
|
|
|
|
unsigned int start;
|
|
|
|
*pkts = 0;
|
|
|
|
*bytes = 0;
|
|
|
|
|
|
|
|
if (!ring)
|
|
|
|
return;
|
|
|
|
do {
|
|
|
|
start = u64_stats_fetch_begin_irq(&ring->syncp);
|
|
|
|
*pkts = ring->stats.pkts;
|
|
|
|
*bytes = ring->stats.bytes;
|
|
|
|
} while (u64_stats_fetch_retry_irq(&ring->syncp, start));
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_update_vsi_ring_stats - Update VSI stats counters
|
|
|
|
* @vsi: the VSI to be updated
|
|
|
|
*/
|
|
|
|
static void ice_update_vsi_ring_stats(struct ice_vsi *vsi)
|
|
|
|
{
|
|
|
|
struct rtnl_link_stats64 *vsi_stats = &vsi->net_stats;
|
|
|
|
struct ice_ring *ring;
|
|
|
|
u64 pkts, bytes;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
/* reset netdev stats */
|
|
|
|
vsi_stats->tx_packets = 0;
|
|
|
|
vsi_stats->tx_bytes = 0;
|
|
|
|
vsi_stats->rx_packets = 0;
|
|
|
|
vsi_stats->rx_bytes = 0;
|
|
|
|
|
|
|
|
/* reset non-netdev (extended) stats */
|
|
|
|
vsi->tx_restart = 0;
|
|
|
|
vsi->tx_busy = 0;
|
|
|
|
vsi->tx_linearize = 0;
|
|
|
|
vsi->rx_buf_failed = 0;
|
|
|
|
vsi->rx_page_failed = 0;
|
|
|
|
|
|
|
|
rcu_read_lock();
|
|
|
|
|
|
|
|
/* update Tx rings counters */
|
|
|
|
ice_for_each_txq(vsi, i) {
|
|
|
|
ring = READ_ONCE(vsi->tx_rings[i]);
|
|
|
|
ice_fetch_u64_stats_per_ring(ring, &pkts, &bytes);
|
|
|
|
vsi_stats->tx_packets += pkts;
|
|
|
|
vsi_stats->tx_bytes += bytes;
|
|
|
|
vsi->tx_restart += ring->tx_stats.restart_q;
|
|
|
|
vsi->tx_busy += ring->tx_stats.tx_busy;
|
|
|
|
vsi->tx_linearize += ring->tx_stats.tx_linearize;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* update Rx rings counters */
|
|
|
|
ice_for_each_rxq(vsi, i) {
|
|
|
|
ring = READ_ONCE(vsi->rx_rings[i]);
|
|
|
|
ice_fetch_u64_stats_per_ring(ring, &pkts, &bytes);
|
|
|
|
vsi_stats->rx_packets += pkts;
|
|
|
|
vsi_stats->rx_bytes += bytes;
|
|
|
|
vsi->rx_buf_failed += ring->rx_stats.alloc_buf_failed;
|
|
|
|
vsi->rx_page_failed += ring->rx_stats.alloc_page_failed;
|
|
|
|
}
|
|
|
|
|
|
|
|
rcu_read_unlock();
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_update_vsi_stats - Update VSI stats counters
|
|
|
|
* @vsi: the VSI to be updated
|
|
|
|
*/
|
|
|
|
static void ice_update_vsi_stats(struct ice_vsi *vsi)
|
|
|
|
{
|
|
|
|
struct rtnl_link_stats64 *cur_ns = &vsi->net_stats;
|
|
|
|
struct ice_eth_stats *cur_es = &vsi->eth_stats;
|
|
|
|
struct ice_pf *pf = vsi->back;
|
|
|
|
|
|
|
|
if (test_bit(__ICE_DOWN, vsi->state) ||
|
|
|
|
test_bit(__ICE_CFG_BUSY, pf->state))
|
|
|
|
return;
|
|
|
|
|
|
|
|
/* get stats as recorded by Tx/Rx rings */
|
|
|
|
ice_update_vsi_ring_stats(vsi);
|
|
|
|
|
|
|
|
/* get VSI stats as recorded by the hardware */
|
|
|
|
ice_update_eth_stats(vsi);
|
|
|
|
|
|
|
|
cur_ns->tx_errors = cur_es->tx_errors;
|
|
|
|
cur_ns->rx_dropped = cur_es->rx_discards;
|
|
|
|
cur_ns->tx_dropped = cur_es->tx_discards;
|
|
|
|
cur_ns->multicast = cur_es->rx_multicast;
|
|
|
|
|
|
|
|
/* update some more netdev stats if this is main VSI */
|
|
|
|
if (vsi->type == ICE_VSI_PF) {
|
|
|
|
cur_ns->rx_crc_errors = pf->stats.crc_errors;
|
|
|
|
cur_ns->rx_errors = pf->stats.crc_errors +
|
|
|
|
pf->stats.illegal_bytes;
|
|
|
|
cur_ns->rx_length_errors = pf->stats.rx_len_errors;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_update_pf_stats - Update PF port stats counters
|
|
|
|
* @pf: PF whose stats needs to be updated
|
|
|
|
*/
|
|
|
|
static void ice_update_pf_stats(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
struct ice_hw_port_stats *prev_ps, *cur_ps;
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
u8 pf_id;
|
|
|
|
|
|
|
|
prev_ps = &pf->stats_prev;
|
|
|
|
cur_ps = &pf->stats;
|
|
|
|
pf_id = hw->pf_id;
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_GORCH(pf_id), GLPRT_GORCL(pf_id),
|
|
|
|
pf->stat_prev_loaded, &prev_ps->eth.rx_bytes,
|
|
|
|
&cur_ps->eth.rx_bytes);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_UPRCH(pf_id), GLPRT_UPRCL(pf_id),
|
|
|
|
pf->stat_prev_loaded, &prev_ps->eth.rx_unicast,
|
|
|
|
&cur_ps->eth.rx_unicast);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_MPRCH(pf_id), GLPRT_MPRCL(pf_id),
|
|
|
|
pf->stat_prev_loaded, &prev_ps->eth.rx_multicast,
|
|
|
|
&cur_ps->eth.rx_multicast);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_BPRCH(pf_id), GLPRT_BPRCL(pf_id),
|
|
|
|
pf->stat_prev_loaded, &prev_ps->eth.rx_broadcast,
|
|
|
|
&cur_ps->eth.rx_broadcast);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_GOTCH(pf_id), GLPRT_GOTCL(pf_id),
|
|
|
|
pf->stat_prev_loaded, &prev_ps->eth.tx_bytes,
|
|
|
|
&cur_ps->eth.tx_bytes);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_UPTCH(pf_id), GLPRT_UPTCL(pf_id),
|
|
|
|
pf->stat_prev_loaded, &prev_ps->eth.tx_unicast,
|
|
|
|
&cur_ps->eth.tx_unicast);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_MPTCH(pf_id), GLPRT_MPTCL(pf_id),
|
|
|
|
pf->stat_prev_loaded, &prev_ps->eth.tx_multicast,
|
|
|
|
&cur_ps->eth.tx_multicast);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_BPTCH(pf_id), GLPRT_BPTCL(pf_id),
|
|
|
|
pf->stat_prev_loaded, &prev_ps->eth.tx_broadcast,
|
|
|
|
&cur_ps->eth.tx_broadcast);
|
|
|
|
|
|
|
|
ice_stat_update32(hw, GLPRT_TDOLD(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->tx_dropped_link_down,
|
|
|
|
&cur_ps->tx_dropped_link_down);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_PRC64H(pf_id), GLPRT_PRC64L(pf_id),
|
|
|
|
pf->stat_prev_loaded, &prev_ps->rx_size_64,
|
|
|
|
&cur_ps->rx_size_64);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_PRC127H(pf_id), GLPRT_PRC127L(pf_id),
|
|
|
|
pf->stat_prev_loaded, &prev_ps->rx_size_127,
|
|
|
|
&cur_ps->rx_size_127);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_PRC255H(pf_id), GLPRT_PRC255L(pf_id),
|
|
|
|
pf->stat_prev_loaded, &prev_ps->rx_size_255,
|
|
|
|
&cur_ps->rx_size_255);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_PRC511H(pf_id), GLPRT_PRC511L(pf_id),
|
|
|
|
pf->stat_prev_loaded, &prev_ps->rx_size_511,
|
|
|
|
&cur_ps->rx_size_511);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_PRC1023H(pf_id),
|
|
|
|
GLPRT_PRC1023L(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->rx_size_1023, &cur_ps->rx_size_1023);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_PRC1522H(pf_id),
|
|
|
|
GLPRT_PRC1522L(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->rx_size_1522, &cur_ps->rx_size_1522);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_PRC9522H(pf_id),
|
|
|
|
GLPRT_PRC9522L(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->rx_size_big, &cur_ps->rx_size_big);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_PTC64H(pf_id), GLPRT_PTC64L(pf_id),
|
|
|
|
pf->stat_prev_loaded, &prev_ps->tx_size_64,
|
|
|
|
&cur_ps->tx_size_64);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_PTC127H(pf_id), GLPRT_PTC127L(pf_id),
|
|
|
|
pf->stat_prev_loaded, &prev_ps->tx_size_127,
|
|
|
|
&cur_ps->tx_size_127);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_PTC255H(pf_id), GLPRT_PTC255L(pf_id),
|
|
|
|
pf->stat_prev_loaded, &prev_ps->tx_size_255,
|
|
|
|
&cur_ps->tx_size_255);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_PTC511H(pf_id), GLPRT_PTC511L(pf_id),
|
|
|
|
pf->stat_prev_loaded, &prev_ps->tx_size_511,
|
|
|
|
&cur_ps->tx_size_511);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_PTC1023H(pf_id),
|
|
|
|
GLPRT_PTC1023L(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->tx_size_1023, &cur_ps->tx_size_1023);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_PTC1522H(pf_id),
|
|
|
|
GLPRT_PTC1522L(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->tx_size_1522, &cur_ps->tx_size_1522);
|
|
|
|
|
|
|
|
ice_stat_update40(hw, GLPRT_PTC9522H(pf_id),
|
|
|
|
GLPRT_PTC9522L(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->tx_size_big, &cur_ps->tx_size_big);
|
|
|
|
|
|
|
|
ice_stat_update32(hw, GLPRT_LXONRXC(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->link_xon_rx, &cur_ps->link_xon_rx);
|
|
|
|
|
|
|
|
ice_stat_update32(hw, GLPRT_LXOFFRXC(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->link_xoff_rx, &cur_ps->link_xoff_rx);
|
|
|
|
|
|
|
|
ice_stat_update32(hw, GLPRT_LXONTXC(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->link_xon_tx, &cur_ps->link_xon_tx);
|
|
|
|
|
|
|
|
ice_stat_update32(hw, GLPRT_LXOFFTXC(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->link_xoff_tx, &cur_ps->link_xoff_tx);
|
|
|
|
|
2019-02-28 15:24:29 -08:00
|
|
|
ice_update_dcb_stats(pf);
|
|
|
|
|
2018-03-20 07:58:16 -07:00
|
|
|
ice_stat_update32(hw, GLPRT_CRCERRS(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->crc_errors, &cur_ps->crc_errors);
|
|
|
|
|
|
|
|
ice_stat_update32(hw, GLPRT_ILLERRC(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->illegal_bytes, &cur_ps->illegal_bytes);
|
|
|
|
|
|
|
|
ice_stat_update32(hw, GLPRT_MLFC(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->mac_local_faults,
|
|
|
|
&cur_ps->mac_local_faults);
|
|
|
|
|
|
|
|
ice_stat_update32(hw, GLPRT_MRFC(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->mac_remote_faults,
|
|
|
|
&cur_ps->mac_remote_faults);
|
|
|
|
|
|
|
|
ice_stat_update32(hw, GLPRT_RLEC(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->rx_len_errors, &cur_ps->rx_len_errors);
|
|
|
|
|
|
|
|
ice_stat_update32(hw, GLPRT_RUC(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->rx_undersize, &cur_ps->rx_undersize);
|
|
|
|
|
|
|
|
ice_stat_update32(hw, GLPRT_RFC(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->rx_fragments, &cur_ps->rx_fragments);
|
|
|
|
|
|
|
|
ice_stat_update32(hw, GLPRT_ROC(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->rx_oversize, &cur_ps->rx_oversize);
|
|
|
|
|
|
|
|
ice_stat_update32(hw, GLPRT_RJC(pf_id), pf->stat_prev_loaded,
|
|
|
|
&prev_ps->rx_jabber, &cur_ps->rx_jabber);
|
|
|
|
|
|
|
|
pf->stat_prev_loaded = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_get_stats64 - get statistics for network device structure
|
|
|
|
* @netdev: network interface device structure
|
|
|
|
* @stats: main device statistics structure
|
|
|
|
*/
|
|
|
|
static
|
|
|
|
void ice_get_stats64(struct net_device *netdev, struct rtnl_link_stats64 *stats)
|
|
|
|
{
|
|
|
|
struct ice_netdev_priv *np = netdev_priv(netdev);
|
|
|
|
struct rtnl_link_stats64 *vsi_stats;
|
|
|
|
struct ice_vsi *vsi = np->vsi;
|
|
|
|
|
|
|
|
vsi_stats = &vsi->net_stats;
|
|
|
|
|
|
|
|
if (test_bit(__ICE_DOWN, vsi->state) || !vsi->num_txq || !vsi->num_rxq)
|
|
|
|
return;
|
|
|
|
/* netdev packet/byte stats come from ring counter. These are obtained
|
|
|
|
* by summing up ring counters (done by ice_update_vsi_ring_stats).
|
|
|
|
*/
|
|
|
|
ice_update_vsi_ring_stats(vsi);
|
|
|
|
stats->tx_packets = vsi_stats->tx_packets;
|
|
|
|
stats->tx_bytes = vsi_stats->tx_bytes;
|
|
|
|
stats->rx_packets = vsi_stats->rx_packets;
|
|
|
|
stats->rx_bytes = vsi_stats->rx_bytes;
|
|
|
|
|
|
|
|
/* The rest of the stats can be read from the hardware but instead we
|
|
|
|
* just return values that the watchdog task has already obtained from
|
|
|
|
* the hardware.
|
|
|
|
*/
|
|
|
|
stats->multicast = vsi_stats->multicast;
|
|
|
|
stats->tx_errors = vsi_stats->tx_errors;
|
|
|
|
stats->tx_dropped = vsi_stats->tx_dropped;
|
|
|
|
stats->rx_errors = vsi_stats->rx_errors;
|
|
|
|
stats->rx_dropped = vsi_stats->rx_dropped;
|
|
|
|
stats->rx_crc_errors = vsi_stats->rx_crc_errors;
|
|
|
|
stats->rx_length_errors = vsi_stats->rx_length_errors;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:14 -07:00
|
|
|
/**
|
|
|
|
* ice_napi_disable_all - Disable NAPI for all q_vectors in the VSI
|
|
|
|
* @vsi: VSI having NAPI disabled
|
|
|
|
*/
|
|
|
|
static void ice_napi_disable_all(struct ice_vsi *vsi)
|
|
|
|
{
|
|
|
|
int q_idx;
|
|
|
|
|
|
|
|
if (!vsi->netdev)
|
|
|
|
return;
|
|
|
|
|
2019-02-28 15:25:53 -08:00
|
|
|
ice_for_each_q_vector(vsi, q_idx) {
|
2018-11-29 01:54:10 +00:00
|
|
|
struct ice_q_vector *q_vector = vsi->q_vectors[q_idx];
|
|
|
|
|
|
|
|
if (q_vector->rx.ring || q_vector->tx.ring)
|
|
|
|
napi_disable(&q_vector->napi);
|
|
|
|
}
|
2018-03-20 07:58:14 -07:00
|
|
|
}
|
|
|
|
|
2018-12-19 10:03:25 -08:00
|
|
|
/**
|
|
|
|
* ice_force_phys_link_state - Force the physical link state
|
|
|
|
* @vsi: VSI to force the physical link state to up/down
|
|
|
|
* @link_up: true/false indicates to set the physical link to up/down
|
|
|
|
*
|
|
|
|
* Force the physical link state by getting the current PHY capabilities from
|
|
|
|
* hardware and setting the PHY config based on the determined capabilities. If
|
|
|
|
* link changes a link event will be triggered because both the Enable Automatic
|
|
|
|
* Link Update and LESM Enable bits are set when setting the PHY capabilities.
|
|
|
|
*
|
|
|
|
* Returns 0 on success, negative on failure
|
|
|
|
*/
|
|
|
|
static int ice_force_phys_link_state(struct ice_vsi *vsi, bool link_up)
|
|
|
|
{
|
|
|
|
struct ice_aqc_get_phy_caps_data *pcaps;
|
|
|
|
struct ice_aqc_set_phy_cfg_data *cfg;
|
|
|
|
struct ice_port_info *pi;
|
|
|
|
struct device *dev;
|
|
|
|
int retcode;
|
|
|
|
|
|
|
|
if (!vsi || !vsi->port_info || !vsi->back)
|
|
|
|
return -EINVAL;
|
|
|
|
if (vsi->type != ICE_VSI_PF)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
dev = &vsi->back->pdev->dev;
|
|
|
|
|
|
|
|
pi = vsi->port_info;
|
|
|
|
|
|
|
|
pcaps = devm_kzalloc(dev, sizeof(*pcaps), GFP_KERNEL);
|
|
|
|
if (!pcaps)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
retcode = ice_aq_get_phy_caps(pi, false, ICE_AQC_REPORT_SW_CFG, pcaps,
|
|
|
|
NULL);
|
|
|
|
if (retcode) {
|
|
|
|
dev_err(dev,
|
|
|
|
"Failed to get phy capabilities, VSI %d error %d\n",
|
|
|
|
vsi->vsi_num, retcode);
|
|
|
|
retcode = -EIO;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* No change in link */
|
|
|
|
if (link_up == !!(pcaps->caps & ICE_AQC_PHY_EN_LINK) &&
|
|
|
|
link_up == !!(pi->phy.link_info.link_info & ICE_AQ_LINK_UP))
|
|
|
|
goto out;
|
|
|
|
|
|
|
|
cfg = devm_kzalloc(dev, sizeof(*cfg), GFP_KERNEL);
|
|
|
|
if (!cfg) {
|
|
|
|
retcode = -ENOMEM;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
cfg->phy_type_low = pcaps->phy_type_low;
|
|
|
|
cfg->phy_type_high = pcaps->phy_type_high;
|
|
|
|
cfg->caps = pcaps->caps | ICE_AQ_PHY_ENA_AUTO_LINK_UPDT;
|
|
|
|
cfg->low_power_ctrl = pcaps->low_power_ctrl;
|
|
|
|
cfg->eee_cap = pcaps->eee_cap;
|
|
|
|
cfg->eeer_value = pcaps->eeer_value;
|
|
|
|
cfg->link_fec_opt = pcaps->link_fec_options;
|
|
|
|
if (link_up)
|
|
|
|
cfg->caps |= ICE_AQ_PHY_ENA_LINK;
|
|
|
|
else
|
|
|
|
cfg->caps &= ~ICE_AQ_PHY_ENA_LINK;
|
|
|
|
|
|
|
|
retcode = ice_aq_set_phy_cfg(&vsi->back->hw, pi->lport, cfg, NULL);
|
|
|
|
if (retcode) {
|
|
|
|
dev_err(dev, "Failed to set phy config, VSI %d error %d\n",
|
|
|
|
vsi->vsi_num, retcode);
|
|
|
|
retcode = -EIO;
|
|
|
|
}
|
|
|
|
|
|
|
|
devm_kfree(dev, cfg);
|
|
|
|
out:
|
|
|
|
devm_kfree(dev, pcaps);
|
|
|
|
return retcode;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:13 -07:00
|
|
|
/**
|
|
|
|
* ice_down - Shutdown the connection
|
|
|
|
* @vsi: The VSI being stopped
|
|
|
|
*/
|
2018-03-20 07:58:16 -07:00
|
|
|
int ice_down(struct ice_vsi *vsi)
|
2018-03-20 07:58:13 -07:00
|
|
|
{
|
2018-12-19 10:03:26 -08:00
|
|
|
int i, tx_err, rx_err, link_err = 0;
|
2018-03-20 07:58:13 -07:00
|
|
|
|
|
|
|
/* Caller of this function is expected to set the
|
|
|
|
* vsi->state __ICE_DOWN bit
|
|
|
|
*/
|
|
|
|
if (vsi->netdev) {
|
|
|
|
netif_carrier_off(vsi->netdev);
|
|
|
|
netif_tx_disable(vsi->netdev);
|
|
|
|
}
|
|
|
|
|
|
|
|
ice_vsi_dis_irq(vsi);
|
2018-12-19 10:03:27 -08:00
|
|
|
|
|
|
|
tx_err = ice_vsi_stop_lan_tx_rings(vsi, ICE_NO_RESET, 0);
|
2018-09-19 17:23:05 -07:00
|
|
|
if (tx_err)
|
|
|
|
netdev_err(vsi->netdev,
|
|
|
|
"Failed stop Tx rings, VSI %d error %d\n",
|
|
|
|
vsi->vsi_num, tx_err);
|
|
|
|
|
|
|
|
rx_err = ice_vsi_stop_rx_rings(vsi);
|
|
|
|
if (rx_err)
|
|
|
|
netdev_err(vsi->netdev,
|
|
|
|
"Failed stop Rx rings, VSI %d error %d\n",
|
|
|
|
vsi->vsi_num, rx_err);
|
|
|
|
|
2018-03-20 07:58:14 -07:00
|
|
|
ice_napi_disable_all(vsi);
|
2018-03-20 07:58:13 -07:00
|
|
|
|
2018-12-19 10:03:26 -08:00
|
|
|
if (test_bit(ICE_FLAG_LINK_DOWN_ON_CLOSE_ENA, vsi->back->flags)) {
|
|
|
|
link_err = ice_force_phys_link_state(vsi, false);
|
|
|
|
if (link_err)
|
|
|
|
netdev_err(vsi->netdev,
|
|
|
|
"Failed to set physical link down, VSI %d error %d\n",
|
|
|
|
vsi->vsi_num, link_err);
|
|
|
|
}
|
2018-12-19 10:03:25 -08:00
|
|
|
|
2018-03-20 07:58:13 -07:00
|
|
|
ice_for_each_txq(vsi, i)
|
|
|
|
ice_clean_tx_ring(vsi->tx_rings[i]);
|
|
|
|
|
|
|
|
ice_for_each_rxq(vsi, i)
|
|
|
|
ice_clean_rx_ring(vsi->rx_rings[i]);
|
|
|
|
|
2018-12-19 10:03:25 -08:00
|
|
|
if (tx_err || rx_err || link_err) {
|
2018-09-19 17:23:05 -07:00
|
|
|
netdev_err(vsi->netdev,
|
|
|
|
"Failed to close VSI 0x%04X on switch 0x%04X\n",
|
2018-03-20 07:58:13 -07:00
|
|
|
vsi->vsi_num, vsi->vsw->sw_id);
|
2018-09-19 17:23:05 -07:00
|
|
|
return -EIO;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
2018-03-20 07:58:13 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_vsi_setup_tx_rings - Allocate VSI Tx queue resources
|
|
|
|
* @vsi: VSI having resources allocated
|
|
|
|
*
|
|
|
|
* Return 0 on success, negative on failure
|
|
|
|
*/
|
2019-04-16 10:30:43 -07:00
|
|
|
int ice_vsi_setup_tx_rings(struct ice_vsi *vsi)
|
2018-03-20 07:58:13 -07:00
|
|
|
{
|
2018-08-09 06:29:01 -07:00
|
|
|
int i, err = 0;
|
2018-03-20 07:58:13 -07:00
|
|
|
|
|
|
|
if (!vsi->num_txq) {
|
|
|
|
dev_err(&vsi->back->pdev->dev, "VSI %d has 0 Tx queues\n",
|
|
|
|
vsi->vsi_num);
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
ice_for_each_txq(vsi, i) {
|
2018-09-19 17:23:05 -07:00
|
|
|
vsi->tx_rings[i]->netdev = vsi->netdev;
|
2018-03-20 07:58:13 -07:00
|
|
|
err = ice_setup_tx_ring(vsi->tx_rings[i]);
|
|
|
|
if (err)
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_vsi_setup_rx_rings - Allocate VSI Rx queue resources
|
|
|
|
* @vsi: VSI having resources allocated
|
|
|
|
*
|
|
|
|
* Return 0 on success, negative on failure
|
|
|
|
*/
|
2019-04-16 10:30:43 -07:00
|
|
|
int ice_vsi_setup_rx_rings(struct ice_vsi *vsi)
|
2018-03-20 07:58:13 -07:00
|
|
|
{
|
2018-08-09 06:29:01 -07:00
|
|
|
int i, err = 0;
|
2018-03-20 07:58:13 -07:00
|
|
|
|
|
|
|
if (!vsi->num_rxq) {
|
|
|
|
dev_err(&vsi->back->pdev->dev, "VSI %d has 0 Rx queues\n",
|
|
|
|
vsi->vsi_num);
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
ice_for_each_rxq(vsi, i) {
|
2018-09-19 17:23:05 -07:00
|
|
|
vsi->rx_rings[i]->netdev = vsi->netdev;
|
2018-03-20 07:58:13 -07:00
|
|
|
err = ice_setup_rx_ring(vsi->rx_rings[i]);
|
|
|
|
if (err)
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_vsi_req_irq - Request IRQ from the OS
|
|
|
|
* @vsi: The VSI IRQ is being requested for
|
|
|
|
* @basename: name for the vector
|
|
|
|
*
|
|
|
|
* Return 0 on success and a negative value on error
|
|
|
|
*/
|
|
|
|
static int ice_vsi_req_irq(struct ice_vsi *vsi, char *basename)
|
|
|
|
{
|
|
|
|
struct ice_pf *pf = vsi->back;
|
|
|
|
int err = -EINVAL;
|
|
|
|
|
|
|
|
if (test_bit(ICE_FLAG_MSIX_ENA, pf->flags))
|
|
|
|
err = ice_vsi_req_irq_msix(vsi, basename);
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_vsi_open - Called when a network interface is made active
|
|
|
|
* @vsi: the VSI to open
|
|
|
|
*
|
|
|
|
* Initialization of the VSI
|
|
|
|
*
|
|
|
|
* Returns 0 on success, negative value on error
|
|
|
|
*/
|
|
|
|
static int ice_vsi_open(struct ice_vsi *vsi)
|
|
|
|
{
|
|
|
|
char int_name[ICE_INT_NAME_STR_LEN];
|
|
|
|
struct ice_pf *pf = vsi->back;
|
|
|
|
int err;
|
|
|
|
|
|
|
|
/* allocate descriptors */
|
|
|
|
err = ice_vsi_setup_tx_rings(vsi);
|
|
|
|
if (err)
|
|
|
|
goto err_setup_tx;
|
|
|
|
|
|
|
|
err = ice_vsi_setup_rx_rings(vsi);
|
|
|
|
if (err)
|
|
|
|
goto err_setup_rx;
|
|
|
|
|
|
|
|
err = ice_vsi_cfg(vsi);
|
|
|
|
if (err)
|
|
|
|
goto err_setup_rx;
|
|
|
|
|
|
|
|
snprintf(int_name, sizeof(int_name) - 1, "%s-%s",
|
|
|
|
dev_driver_string(&pf->pdev->dev), vsi->netdev->name);
|
|
|
|
err = ice_vsi_req_irq(vsi, int_name);
|
|
|
|
if (err)
|
|
|
|
goto err_setup_rx;
|
|
|
|
|
|
|
|
/* Notify the stack of the actual queue counts. */
|
|
|
|
err = netif_set_real_num_tx_queues(vsi->netdev, vsi->num_txq);
|
|
|
|
if (err)
|
|
|
|
goto err_set_qs;
|
|
|
|
|
|
|
|
err = netif_set_real_num_rx_queues(vsi->netdev, vsi->num_rxq);
|
|
|
|
if (err)
|
|
|
|
goto err_set_qs;
|
|
|
|
|
|
|
|
err = ice_up_complete(vsi);
|
|
|
|
if (err)
|
|
|
|
goto err_up_complete;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
err_up_complete:
|
|
|
|
ice_down(vsi);
|
|
|
|
err_set_qs:
|
|
|
|
ice_vsi_free_irq(vsi);
|
|
|
|
err_setup_rx:
|
|
|
|
ice_vsi_free_rx_rings(vsi);
|
|
|
|
err_setup_tx:
|
|
|
|
ice_vsi_free_tx_rings(vsi);
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
2018-08-09 06:29:50 -07:00
|
|
|
/**
|
|
|
|
* ice_vsi_release_all - Delete all VSIs
|
|
|
|
* @pf: PF from which all VSIs are being removed
|
|
|
|
*/
|
|
|
|
static void ice_vsi_release_all(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
int err, i;
|
|
|
|
|
|
|
|
if (!pf->vsi)
|
|
|
|
return;
|
|
|
|
|
2019-02-08 12:50:54 -08:00
|
|
|
ice_for_each_vsi(pf, i) {
|
2018-08-09 06:29:50 -07:00
|
|
|
if (!pf->vsi[i])
|
|
|
|
continue;
|
|
|
|
|
|
|
|
err = ice_vsi_release(pf->vsi[i]);
|
|
|
|
if (err)
|
|
|
|
dev_dbg(&pf->pdev->dev,
|
|
|
|
"Failed to release pf->vsi[%d], err %d, vsi_num = %d\n",
|
|
|
|
i, err, pf->vsi[i]->vsi_num);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:18 -07:00
|
|
|
/**
|
2019-02-28 15:24:24 -08:00
|
|
|
* ice_ena_vsi - resume a VSI
|
|
|
|
* @vsi: the VSI being resume
|
2018-10-26 10:41:04 -07:00
|
|
|
* @locked: is the rtnl_lock already held
|
2018-03-20 07:58:18 -07:00
|
|
|
*/
|
2019-02-28 15:24:24 -08:00
|
|
|
static int ice_ena_vsi(struct ice_vsi *vsi, bool locked)
|
2018-03-20 07:58:18 -07:00
|
|
|
{
|
2019-02-28 15:24:24 -08:00
|
|
|
int err = 0;
|
2018-03-20 07:58:18 -07:00
|
|
|
|
2019-02-28 15:24:24 -08:00
|
|
|
if (!test_bit(__ICE_NEEDS_RESTART, vsi->state))
|
|
|
|
return err;
|
|
|
|
|
|
|
|
clear_bit(__ICE_NEEDS_RESTART, vsi->state);
|
|
|
|
|
|
|
|
if (vsi->netdev && vsi->type == ICE_VSI_PF) {
|
|
|
|
struct net_device *netd = vsi->netdev;
|
2018-03-20 07:58:18 -07:00
|
|
|
|
2018-09-19 17:43:06 -07:00
|
|
|
if (netif_running(vsi->netdev)) {
|
2019-02-28 15:24:24 -08:00
|
|
|
if (locked) {
|
|
|
|
err = netd->netdev_ops->ndo_open(netd);
|
|
|
|
} else {
|
2018-10-26 10:41:04 -07:00
|
|
|
rtnl_lock();
|
2019-02-28 15:24:24 -08:00
|
|
|
err = netd->netdev_ops->ndo_open(netd);
|
2018-10-26 10:41:04 -07:00
|
|
|
rtnl_unlock();
|
|
|
|
}
|
2018-09-19 17:43:06 -07:00
|
|
|
} else {
|
|
|
|
err = ice_vsi_open(vsi);
|
2018-08-09 06:29:50 -07:00
|
|
|
}
|
2018-09-19 17:43:06 -07:00
|
|
|
}
|
2018-03-20 07:58:18 -07:00
|
|
|
|
2018-08-09 06:29:50 -07:00
|
|
|
return err;
|
2018-03-20 07:58:18 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_pf_ena_all_vsi - Resume all VSIs on a PF
|
|
|
|
* @pf: the PF
|
2019-02-28 15:24:24 -08:00
|
|
|
* @locked: is the rtnl_lock already held
|
2018-03-20 07:58:18 -07:00
|
|
|
*/
|
2019-02-28 15:24:24 -08:00
|
|
|
#ifdef CONFIG_DCB
|
|
|
|
int ice_pf_ena_all_vsi(struct ice_pf *pf, bool locked)
|
|
|
|
#else
|
|
|
|
static int ice_pf_ena_all_vsi(struct ice_pf *pf, bool locked)
|
|
|
|
#endif /* CONFIG_DCB */
|
2018-03-20 07:58:18 -07:00
|
|
|
{
|
|
|
|
int v;
|
|
|
|
|
|
|
|
ice_for_each_vsi(pf, v)
|
|
|
|
if (pf->vsi[v])
|
2019-02-28 15:24:24 -08:00
|
|
|
if (ice_ena_vsi(pf->vsi[v], locked))
|
2018-08-09 06:29:50 -07:00
|
|
|
return -EIO;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_vsi_rebuild_all - rebuild all VSIs in pf
|
|
|
|
* @pf: the PF
|
|
|
|
*/
|
|
|
|
static int ice_vsi_rebuild_all(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
|
|
|
/* loop through pf->vsi array and reinit the VSI if found */
|
2019-02-08 12:50:54 -08:00
|
|
|
ice_for_each_vsi(pf, i) {
|
2018-08-09 06:29:50 -07:00
|
|
|
int err;
|
|
|
|
|
|
|
|
if (!pf->vsi[i])
|
|
|
|
continue;
|
|
|
|
|
|
|
|
err = ice_vsi_rebuild(pf->vsi[i]);
|
|
|
|
if (err) {
|
|
|
|
dev_err(&pf->pdev->dev,
|
|
|
|
"VSI at index %d rebuild failed\n",
|
|
|
|
pf->vsi[i]->idx);
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
dev_info(&pf->pdev->dev,
|
|
|
|
"VSI at index %d rebuilt. vsi_num = 0x%x\n",
|
|
|
|
pf->vsi[i]->idx, pf->vsi[i]->vsi_num);
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
2018-03-20 07:58:18 -07:00
|
|
|
}
|
|
|
|
|
ice: Implement VSI replay framework
Currently, switch filters get replayed after reset. In addition to
filters, other VSI attributes (like RSS configuration, Tx scheduler
configuration, etc.) also need to be replayed after reset.
Thus, instead of replaying based on functional blocks (i.e. replay
all filters for all VSIs, followed by RSS configuration replay for
all VSIs, and so on), it makes more sense to have the replay centered
around a VSI. In other words, replay all configurations for a VSI before
moving on to rebuilding the next VSI.
To that effect, this patch introduces a VSI replay framework in a new
function ice_vsi_replay_all. Currently it only replays switch filters,
but it will be expanded in the future to replay additional VSI attributes.
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-09-19 17:23:14 -07:00
|
|
|
/**
|
|
|
|
* ice_vsi_replay_all - replay all VSIs configuration in the PF
|
|
|
|
* @pf: the PF
|
|
|
|
*/
|
|
|
|
static int ice_vsi_replay_all(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
enum ice_status ret;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
/* loop through pf->vsi array and replay the VSI if found */
|
2019-02-08 12:50:54 -08:00
|
|
|
ice_for_each_vsi(pf, i) {
|
ice: Implement VSI replay framework
Currently, switch filters get replayed after reset. In addition to
filters, other VSI attributes (like RSS configuration, Tx scheduler
configuration, etc.) also need to be replayed after reset.
Thus, instead of replaying based on functional blocks (i.e. replay
all filters for all VSIs, followed by RSS configuration replay for
all VSIs, and so on), it makes more sense to have the replay centered
around a VSI. In other words, replay all configurations for a VSI before
moving on to rebuilding the next VSI.
To that effect, this patch introduces a VSI replay framework in a new
function ice_vsi_replay_all. Currently it only replays switch filters,
but it will be expanded in the future to replay additional VSI attributes.
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-09-19 17:23:14 -07:00
|
|
|
if (!pf->vsi[i])
|
|
|
|
continue;
|
|
|
|
|
|
|
|
ret = ice_replay_vsi(hw, pf->vsi[i]->idx);
|
|
|
|
if (ret) {
|
|
|
|
dev_err(&pf->pdev->dev,
|
|
|
|
"VSI at index %d replay failed %d\n",
|
|
|
|
pf->vsi[i]->idx, ret);
|
|
|
|
return -EIO;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Re-map HW VSI number, using VSI handle that has been
|
|
|
|
* previously validated in ice_replay_vsi() call above
|
|
|
|
*/
|
|
|
|
pf->vsi[i]->vsi_num = ice_get_hw_vsi_num(hw, pf->vsi[i]->idx);
|
|
|
|
|
|
|
|
dev_info(&pf->pdev->dev,
|
|
|
|
"VSI at index %d filter replayed successfully - vsi_num %i\n",
|
|
|
|
pf->vsi[i]->idx, pf->vsi[i]->vsi_num);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Clean up replay filter after successful re-configuration */
|
|
|
|
ice_replay_post(hw);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:18 -07:00
|
|
|
/**
|
|
|
|
* ice_rebuild - rebuild after reset
|
|
|
|
* @pf: pf to rebuild
|
|
|
|
*/
|
|
|
|
static void ice_rebuild(struct ice_pf *pf)
|
|
|
|
{
|
|
|
|
struct device *dev = &pf->pdev->dev;
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
enum ice_status ret;
|
2018-10-26 10:40:50 -07:00
|
|
|
int err, i;
|
2018-03-20 07:58:18 -07:00
|
|
|
|
|
|
|
if (test_bit(__ICE_DOWN, pf->state))
|
|
|
|
goto clear_recovery;
|
|
|
|
|
|
|
|
dev_dbg(dev, "rebuilding pf\n");
|
|
|
|
|
|
|
|
ret = ice_init_all_ctrlq(hw);
|
|
|
|
if (ret) {
|
|
|
|
dev_err(dev, "control queues init failed %d\n", ret);
|
2018-08-09 06:29:50 -07:00
|
|
|
goto err_init_ctrlq;
|
2018-03-20 07:58:18 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
ret = ice_clear_pf_cfg(hw);
|
|
|
|
if (ret) {
|
|
|
|
dev_err(dev, "clear PF configuration failed %d\n", ret);
|
2018-08-09 06:29:50 -07:00
|
|
|
goto err_init_ctrlq;
|
2018-03-20 07:58:18 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
ice_clear_pxe_mode(hw);
|
|
|
|
|
|
|
|
ret = ice_get_caps(hw);
|
|
|
|
if (ret) {
|
|
|
|
dev_err(dev, "ice_get_caps failed %d\n", ret);
|
2018-08-09 06:29:50 -07:00
|
|
|
goto err_init_ctrlq;
|
2018-03-20 07:58:18 -07:00
|
|
|
}
|
|
|
|
|
2018-08-09 06:29:50 -07:00
|
|
|
err = ice_sched_init_port(hw->port_info);
|
|
|
|
if (err)
|
|
|
|
goto err_sched_init_port;
|
|
|
|
|
2019-02-28 15:24:30 -08:00
|
|
|
ice_dcb_rebuild(pf);
|
|
|
|
|
2018-08-09 06:29:50 -07:00
|
|
|
err = ice_vsi_rebuild_all(pf);
|
2018-03-20 07:58:18 -07:00
|
|
|
if (err) {
|
2018-08-09 06:29:50 -07:00
|
|
|
dev_err(dev, "ice_vsi_rebuild_all failed\n");
|
|
|
|
goto err_vsi_rebuild;
|
|
|
|
}
|
|
|
|
|
2018-09-19 17:23:15 -07:00
|
|
|
err = ice_update_link_info(hw->port_info);
|
|
|
|
if (err)
|
|
|
|
dev_err(&pf->pdev->dev, "Get link status error %d\n", err);
|
|
|
|
|
ice: Implement VSI replay framework
Currently, switch filters get replayed after reset. In addition to
filters, other VSI attributes (like RSS configuration, Tx scheduler
configuration, etc.) also need to be replayed after reset.
Thus, instead of replaying based on functional blocks (i.e. replay
all filters for all VSIs, followed by RSS configuration replay for
all VSIs, and so on), it makes more sense to have the replay centered
around a VSI. In other words, replay all configurations for a VSI before
moving on to rebuilding the next VSI.
To that effect, this patch introduces a VSI replay framework in a new
function ice_vsi_replay_all. Currently it only replays switch filters,
but it will be expanded in the future to replay additional VSI attributes.
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-09-19 17:23:14 -07:00
|
|
|
/* Replay all VSIs Configuration, including filters after reset */
|
|
|
|
if (ice_vsi_replay_all(pf)) {
|
2018-08-09 06:29:50 -07:00
|
|
|
dev_err(&pf->pdev->dev,
|
ice: Implement VSI replay framework
Currently, switch filters get replayed after reset. In addition to
filters, other VSI attributes (like RSS configuration, Tx scheduler
configuration, etc.) also need to be replayed after reset.
Thus, instead of replaying based on functional blocks (i.e. replay
all filters for all VSIs, followed by RSS configuration replay for
all VSIs, and so on), it makes more sense to have the replay centered
around a VSI. In other words, replay all configurations for a VSI before
moving on to rebuilding the next VSI.
To that effect, this patch introduces a VSI replay framework in a new
function ice_vsi_replay_all. Currently it only replays switch filters,
but it will be expanded in the future to replay additional VSI attributes.
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-09-19 17:23:14 -07:00
|
|
|
"error replaying VSI configurations with switch filter rules\n");
|
2018-08-09 06:29:50 -07:00
|
|
|
goto err_vsi_rebuild;
|
2018-03-20 07:58:18 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/* start misc vector */
|
|
|
|
if (test_bit(ICE_FLAG_MSIX_ENA, pf->flags)) {
|
|
|
|
err = ice_req_irq_msix_misc(pf);
|
|
|
|
if (err) {
|
|
|
|
dev_err(dev, "misc vector setup failed: %d\n", err);
|
2018-08-09 06:29:50 -07:00
|
|
|
goto err_vsi_rebuild;
|
2018-03-20 07:58:18 -07:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* restart the VSIs that were rebuilt and running before the reset */
|
2019-02-28 15:24:24 -08:00
|
|
|
err = ice_pf_ena_all_vsi(pf, false);
|
2018-08-09 06:29:50 -07:00
|
|
|
if (err) {
|
|
|
|
dev_err(&pf->pdev->dev, "error enabling VSIs\n");
|
|
|
|
/* no need to disable VSIs in tear down path in ice_rebuild()
|
|
|
|
* since its already taken care in ice_vsi_open()
|
|
|
|
*/
|
|
|
|
goto err_vsi_rebuild;
|
|
|
|
}
|
2018-03-20 07:58:18 -07:00
|
|
|
|
2019-02-08 12:50:54 -08:00
|
|
|
ice_for_each_vsi(pf, i) {
|
2018-10-26 10:40:50 -07:00
|
|
|
bool link_up;
|
|
|
|
|
|
|
|
if (!pf->vsi[i] || pf->vsi[i]->type != ICE_VSI_PF)
|
|
|
|
continue;
|
|
|
|
ice_get_link_status(pf->vsi[i]->port_info, &link_up);
|
|
|
|
if (link_up) {
|
|
|
|
netif_carrier_on(pf->vsi[i]->netdev);
|
|
|
|
netif_tx_wake_all_queues(pf->vsi[i]->netdev);
|
|
|
|
} else {
|
|
|
|
netif_carrier_off(pf->vsi[i]->netdev);
|
|
|
|
netif_tx_stop_all_queues(pf->vsi[i]->netdev);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-08-09 06:29:50 -07:00
|
|
|
/* if we get here, reset flow is successful */
|
|
|
|
clear_bit(__ICE_RESET_FAILED, pf->state);
|
2018-03-20 07:58:18 -07:00
|
|
|
return;
|
|
|
|
|
2018-08-09 06:29:50 -07:00
|
|
|
err_vsi_rebuild:
|
|
|
|
ice_vsi_release_all(pf);
|
|
|
|
err_sched_init_port:
|
|
|
|
ice_sched_cleanup_all(hw);
|
|
|
|
err_init_ctrlq:
|
2018-03-20 07:58:18 -07:00
|
|
|
ice_shutdown_all_ctrlq(hw);
|
|
|
|
set_bit(__ICE_RESET_FAILED, pf->state);
|
|
|
|
clear_recovery:
|
2018-08-09 06:29:50 -07:00
|
|
|
/* set this bit in PF state to control service task scheduling */
|
|
|
|
set_bit(__ICE_NEEDS_RESTART, pf->state);
|
|
|
|
dev_err(dev, "Rebuild failed, unload and reload driver\n");
|
2018-03-20 07:58:18 -07:00
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:19 -07:00
|
|
|
/**
|
|
|
|
* ice_change_mtu - NDO callback to change the MTU
|
|
|
|
* @netdev: network interface device structure
|
|
|
|
* @new_mtu: new value for maximum frame size
|
|
|
|
*
|
|
|
|
* Returns 0 on success, negative on failure
|
|
|
|
*/
|
|
|
|
static int ice_change_mtu(struct net_device *netdev, int new_mtu)
|
|
|
|
{
|
|
|
|
struct ice_netdev_priv *np = netdev_priv(netdev);
|
|
|
|
struct ice_vsi *vsi = np->vsi;
|
|
|
|
struct ice_pf *pf = vsi->back;
|
|
|
|
u8 count = 0;
|
|
|
|
|
|
|
|
if (new_mtu == netdev->mtu) {
|
2018-08-09 06:29:03 -07:00
|
|
|
netdev_warn(netdev, "mtu is already %u\n", netdev->mtu);
|
2018-03-20 07:58:19 -07:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (new_mtu < netdev->min_mtu) {
|
|
|
|
netdev_err(netdev, "new mtu invalid. min_mtu is %d\n",
|
|
|
|
netdev->min_mtu);
|
|
|
|
return -EINVAL;
|
|
|
|
} else if (new_mtu > netdev->max_mtu) {
|
|
|
|
netdev_err(netdev, "new mtu invalid. max_mtu is %d\n",
|
|
|
|
netdev->min_mtu);
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
/* if a reset is in progress, wait for some time for it to complete */
|
|
|
|
do {
|
2018-09-19 17:23:11 -07:00
|
|
|
if (ice_is_reset_in_progress(pf->state)) {
|
2018-03-20 07:58:19 -07:00
|
|
|
count++;
|
|
|
|
usleep_range(1000, 2000);
|
|
|
|
} else {
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
} while (count < 100);
|
|
|
|
|
|
|
|
if (count == 100) {
|
|
|
|
netdev_err(netdev, "can't change mtu. Device is busy\n");
|
|
|
|
return -EBUSY;
|
|
|
|
}
|
|
|
|
|
|
|
|
netdev->mtu = new_mtu;
|
|
|
|
|
|
|
|
/* if VSI is up, bring it down and then back up */
|
|
|
|
if (!test_and_set_bit(__ICE_DOWN, vsi->state)) {
|
|
|
|
int err;
|
|
|
|
|
|
|
|
err = ice_down(vsi);
|
|
|
|
if (err) {
|
|
|
|
netdev_err(netdev, "change mtu if_up err %d\n", err);
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
err = ice_up(vsi);
|
|
|
|
if (err) {
|
|
|
|
netdev_err(netdev, "change mtu if_up err %d\n", err);
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2019-04-16 10:30:46 -07:00
|
|
|
netdev_info(netdev, "changed MTU to %d\n", new_mtu);
|
2018-03-20 07:58:19 -07:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:15 -07:00
|
|
|
/**
|
|
|
|
* ice_set_rss - Set RSS keys and lut
|
|
|
|
* @vsi: Pointer to VSI structure
|
|
|
|
* @seed: RSS hash seed
|
|
|
|
* @lut: Lookup table
|
|
|
|
* @lut_size: Lookup table size
|
|
|
|
*
|
|
|
|
* Returns 0 on success, negative on failure
|
|
|
|
*/
|
|
|
|
int ice_set_rss(struct ice_vsi *vsi, u8 *seed, u8 *lut, u16 lut_size)
|
|
|
|
{
|
|
|
|
struct ice_pf *pf = vsi->back;
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
enum ice_status status;
|
|
|
|
|
|
|
|
if (seed) {
|
|
|
|
struct ice_aqc_get_set_rss_keys *buf =
|
|
|
|
(struct ice_aqc_get_set_rss_keys *)seed;
|
|
|
|
|
2018-09-19 17:23:13 -07:00
|
|
|
status = ice_aq_set_rss_key(hw, vsi->idx, buf);
|
2018-03-20 07:58:15 -07:00
|
|
|
|
|
|
|
if (status) {
|
|
|
|
dev_err(&pf->pdev->dev,
|
|
|
|
"Cannot set RSS key, err %d aq_err %d\n",
|
|
|
|
status, hw->adminq.rq_last_status);
|
|
|
|
return -EIO;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (lut) {
|
2018-09-19 17:23:13 -07:00
|
|
|
status = ice_aq_set_rss_lut(hw, vsi->idx, vsi->rss_lut_type,
|
|
|
|
lut, lut_size);
|
2018-03-20 07:58:15 -07:00
|
|
|
if (status) {
|
|
|
|
dev_err(&pf->pdev->dev,
|
|
|
|
"Cannot set RSS lut, err %d aq_err %d\n",
|
|
|
|
status, hw->adminq.rq_last_status);
|
|
|
|
return -EIO;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_get_rss - Get RSS keys and lut
|
|
|
|
* @vsi: Pointer to VSI structure
|
|
|
|
* @seed: Buffer to store the keys
|
|
|
|
* @lut: Buffer to store the lookup table entries
|
|
|
|
* @lut_size: Size of buffer to store the lookup table entries
|
|
|
|
*
|
|
|
|
* Returns 0 on success, negative on failure
|
|
|
|
*/
|
|
|
|
int ice_get_rss(struct ice_vsi *vsi, u8 *seed, u8 *lut, u16 lut_size)
|
|
|
|
{
|
|
|
|
struct ice_pf *pf = vsi->back;
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
enum ice_status status;
|
|
|
|
|
|
|
|
if (seed) {
|
|
|
|
struct ice_aqc_get_set_rss_keys *buf =
|
|
|
|
(struct ice_aqc_get_set_rss_keys *)seed;
|
|
|
|
|
2018-09-19 17:23:13 -07:00
|
|
|
status = ice_aq_get_rss_key(hw, vsi->idx, buf);
|
2018-03-20 07:58:15 -07:00
|
|
|
if (status) {
|
|
|
|
dev_err(&pf->pdev->dev,
|
|
|
|
"Cannot get RSS key, err %d aq_err %d\n",
|
|
|
|
status, hw->adminq.rq_last_status);
|
|
|
|
return -EIO;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (lut) {
|
2018-09-19 17:23:13 -07:00
|
|
|
status = ice_aq_get_rss_lut(hw, vsi->idx, vsi->rss_lut_type,
|
|
|
|
lut, lut_size);
|
2018-03-20 07:58:15 -07:00
|
|
|
if (status) {
|
|
|
|
dev_err(&pf->pdev->dev,
|
|
|
|
"Cannot get RSS lut, err %d aq_err %d\n",
|
|
|
|
status, hw->adminq.rq_last_status);
|
|
|
|
return -EIO;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-08-09 06:29:54 -07:00
|
|
|
/**
|
|
|
|
* ice_bridge_getlink - Get the hardware bridge mode
|
|
|
|
* @skb: skb buff
|
2019-02-19 15:04:13 -08:00
|
|
|
* @pid: process ID
|
2018-08-09 06:29:54 -07:00
|
|
|
* @seq: RTNL message seq
|
|
|
|
* @dev: the netdev being configured
|
|
|
|
* @filter_mask: filter mask passed in
|
|
|
|
* @nlflags: netlink flags passed in
|
|
|
|
*
|
|
|
|
* Return the bridge mode (VEB/VEPA)
|
|
|
|
*/
|
|
|
|
static int
|
|
|
|
ice_bridge_getlink(struct sk_buff *skb, u32 pid, u32 seq,
|
|
|
|
struct net_device *dev, u32 filter_mask, int nlflags)
|
|
|
|
{
|
|
|
|
struct ice_netdev_priv *np = netdev_priv(dev);
|
|
|
|
struct ice_vsi *vsi = np->vsi;
|
|
|
|
struct ice_pf *pf = vsi->back;
|
|
|
|
u16 bmode;
|
|
|
|
|
|
|
|
bmode = pf->first_sw->bridge_mode;
|
|
|
|
|
|
|
|
return ndo_dflt_bridge_getlink(skb, pid, seq, dev, bmode, 0, 0, nlflags,
|
|
|
|
filter_mask, NULL);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_vsi_update_bridge_mode - Update VSI for switching bridge mode (VEB/VEPA)
|
|
|
|
* @vsi: Pointer to VSI structure
|
|
|
|
* @bmode: Hardware bridge mode (VEB/VEPA)
|
|
|
|
*
|
|
|
|
* Returns 0 on success, negative on failure
|
|
|
|
*/
|
|
|
|
static int ice_vsi_update_bridge_mode(struct ice_vsi *vsi, u16 bmode)
|
|
|
|
{
|
|
|
|
struct device *dev = &vsi->back->pdev->dev;
|
|
|
|
struct ice_aqc_vsi_props *vsi_props;
|
|
|
|
struct ice_hw *hw = &vsi->back->hw;
|
2019-02-08 12:50:32 -08:00
|
|
|
struct ice_vsi_ctx *ctxt;
|
2018-08-09 06:29:54 -07:00
|
|
|
enum ice_status status;
|
2019-02-08 12:50:32 -08:00
|
|
|
int ret = 0;
|
2018-08-09 06:29:54 -07:00
|
|
|
|
|
|
|
vsi_props = &vsi->info;
|
2019-02-08 12:50:32 -08:00
|
|
|
|
|
|
|
ctxt = devm_kzalloc(dev, sizeof(*ctxt), GFP_KERNEL);
|
|
|
|
if (!ctxt)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
ctxt->info = vsi->info;
|
2018-08-09 06:29:54 -07:00
|
|
|
|
|
|
|
if (bmode == BRIDGE_MODE_VEB)
|
|
|
|
/* change from VEPA to VEB mode */
|
2019-02-08 12:50:32 -08:00
|
|
|
ctxt->info.sw_flags |= ICE_AQ_VSI_SW_FLAG_ALLOW_LB;
|
2018-08-09 06:29:54 -07:00
|
|
|
else
|
|
|
|
/* change from VEB to VEPA mode */
|
2019-02-08 12:50:32 -08:00
|
|
|
ctxt->info.sw_flags &= ~ICE_AQ_VSI_SW_FLAG_ALLOW_LB;
|
|
|
|
ctxt->info.valid_sections = cpu_to_le16(ICE_AQ_VSI_PROP_SW_VALID);
|
2018-09-19 17:23:12 -07:00
|
|
|
|
2019-02-08 12:50:32 -08:00
|
|
|
status = ice_update_vsi(hw, vsi->idx, ctxt, NULL);
|
2018-08-09 06:29:54 -07:00
|
|
|
if (status) {
|
|
|
|
dev_err(dev, "update VSI for bridge mode failed, bmode = %d err %d aq_err %d\n",
|
|
|
|
bmode, status, hw->adminq.sq_last_status);
|
2019-02-08 12:50:32 -08:00
|
|
|
ret = -EIO;
|
|
|
|
goto out;
|
2018-08-09 06:29:54 -07:00
|
|
|
}
|
|
|
|
/* Update sw flags for book keeping */
|
2019-02-08 12:50:32 -08:00
|
|
|
vsi_props->sw_flags = ctxt->info.sw_flags;
|
2018-08-09 06:29:54 -07:00
|
|
|
|
2019-02-08 12:50:32 -08:00
|
|
|
out:
|
|
|
|
devm_kfree(dev, ctxt);
|
|
|
|
return ret;
|
2018-08-09 06:29:54 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_bridge_setlink - Set the hardware bridge mode
|
|
|
|
* @dev: the netdev being configured
|
|
|
|
* @nlh: RTNL message
|
|
|
|
* @flags: bridge setlink flags
|
2018-12-12 17:02:48 +00:00
|
|
|
* @extack: netlink extended ack
|
2018-08-09 06:29:54 -07:00
|
|
|
*
|
|
|
|
* Sets the bridge mode (VEB/VEPA) of the switch to which the netdev (VSI) is
|
|
|
|
* hooked up to. Iterates through the PF VSI list and sets the loopback mode (if
|
|
|
|
* not already set for all VSIs connected to this switch. And also update the
|
|
|
|
* unicast switch filter rules for the corresponding switch of the netdev.
|
|
|
|
*/
|
|
|
|
static int
|
|
|
|
ice_bridge_setlink(struct net_device *dev, struct nlmsghdr *nlh,
|
2018-12-19 10:03:20 -08:00
|
|
|
u16 __always_unused flags,
|
|
|
|
struct netlink_ext_ack __always_unused *extack)
|
2018-08-09 06:29:54 -07:00
|
|
|
{
|
|
|
|
struct ice_netdev_priv *np = netdev_priv(dev);
|
|
|
|
struct ice_pf *pf = np->vsi->back;
|
|
|
|
struct nlattr *attr, *br_spec;
|
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
enum ice_status status;
|
|
|
|
struct ice_sw *pf_sw;
|
|
|
|
int rem, v, err = 0;
|
|
|
|
|
|
|
|
pf_sw = pf->first_sw;
|
|
|
|
/* find the attribute in the netlink message */
|
|
|
|
br_spec = nlmsg_find_attr(nlh, sizeof(struct ifinfomsg), IFLA_AF_SPEC);
|
|
|
|
|
|
|
|
nla_for_each_nested(attr, br_spec, rem) {
|
|
|
|
__u16 mode;
|
|
|
|
|
|
|
|
if (nla_type(attr) != IFLA_BRIDGE_MODE)
|
|
|
|
continue;
|
|
|
|
mode = nla_get_u16(attr);
|
|
|
|
if (mode != BRIDGE_MODE_VEPA && mode != BRIDGE_MODE_VEB)
|
|
|
|
return -EINVAL;
|
|
|
|
/* Continue if bridge mode is not being flipped */
|
|
|
|
if (mode == pf_sw->bridge_mode)
|
|
|
|
continue;
|
|
|
|
/* Iterates through the PF VSI list and update the loopback
|
|
|
|
* mode of the VSI
|
|
|
|
*/
|
|
|
|
ice_for_each_vsi(pf, v) {
|
|
|
|
if (!pf->vsi[v])
|
|
|
|
continue;
|
|
|
|
err = ice_vsi_update_bridge_mode(pf->vsi[v], mode);
|
|
|
|
if (err)
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
hw->evb_veb = (mode == BRIDGE_MODE_VEB);
|
|
|
|
/* Update the unicast switch filter rules for the corresponding
|
|
|
|
* switch of the netdev
|
|
|
|
*/
|
|
|
|
status = ice_update_sw_rule_bridge_mode(hw);
|
|
|
|
if (status) {
|
2018-10-26 11:44:46 -07:00
|
|
|
netdev_err(dev, "switch rule update failed, mode = %d err %d aq_err %d\n",
|
2018-08-09 06:29:54 -07:00
|
|
|
mode, status, hw->adminq.sq_last_status);
|
|
|
|
/* revert hw->evb_veb */
|
|
|
|
hw->evb_veb = (pf_sw->bridge_mode == BRIDGE_MODE_VEB);
|
|
|
|
return -EIO;
|
|
|
|
}
|
|
|
|
|
|
|
|
pf_sw->bridge_mode = mode;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-08-09 06:29:53 -07:00
|
|
|
/**
|
|
|
|
* ice_tx_timeout - Respond to a Tx Hang
|
|
|
|
* @netdev: network interface device structure
|
|
|
|
*/
|
|
|
|
static void ice_tx_timeout(struct net_device *netdev)
|
|
|
|
{
|
|
|
|
struct ice_netdev_priv *np = netdev_priv(netdev);
|
|
|
|
struct ice_ring *tx_ring = NULL;
|
|
|
|
struct ice_vsi *vsi = np->vsi;
|
|
|
|
struct ice_pf *pf = vsi->back;
|
|
|
|
int hung_queue = -1;
|
2018-10-26 10:41:00 -07:00
|
|
|
u32 i;
|
2018-08-09 06:29:53 -07:00
|
|
|
|
|
|
|
pf->tx_timeout_count++;
|
|
|
|
|
2018-10-26 11:44:44 -07:00
|
|
|
/* find the stopped queue the same way dev_watchdog() does */
|
2018-08-09 06:29:53 -07:00
|
|
|
for (i = 0; i < netdev->num_tx_queues; i++) {
|
|
|
|
unsigned long trans_start;
|
2018-10-26 11:44:44 -07:00
|
|
|
struct netdev_queue *q;
|
2018-08-09 06:29:53 -07:00
|
|
|
|
|
|
|
q = netdev_get_tx_queue(netdev, i);
|
|
|
|
trans_start = q->trans_start;
|
|
|
|
if (netif_xmit_stopped(q) &&
|
|
|
|
time_after(jiffies,
|
2018-10-26 11:44:44 -07:00
|
|
|
trans_start + netdev->watchdog_timeo)) {
|
2018-08-09 06:29:53 -07:00
|
|
|
hung_queue = i;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-10-26 11:44:44 -07:00
|
|
|
if (i == netdev->num_tx_queues)
|
2018-08-09 06:29:53 -07:00
|
|
|
netdev_info(netdev, "tx_timeout: no netdev hung queue found\n");
|
2018-10-26 11:44:44 -07:00
|
|
|
else
|
2018-08-09 06:29:53 -07:00
|
|
|
/* now that we have an index, find the tx_ring struct */
|
2018-10-26 11:44:44 -07:00
|
|
|
for (i = 0; i < vsi->num_txq; i++)
|
|
|
|
if (vsi->tx_rings[i] && vsi->tx_rings[i]->desc)
|
|
|
|
if (hung_queue == vsi->tx_rings[i]->q_index) {
|
2018-08-09 06:29:53 -07:00
|
|
|
tx_ring = vsi->tx_rings[i];
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Reset recovery level if enough time has elapsed after last timeout.
|
|
|
|
* Also ensure no new reset action happens before next timeout period.
|
|
|
|
*/
|
|
|
|
if (time_after(jiffies, (pf->tx_timeout_last_recovery + HZ * 20)))
|
|
|
|
pf->tx_timeout_recovery_level = 1;
|
|
|
|
else if (time_before(jiffies, (pf->tx_timeout_last_recovery +
|
|
|
|
netdev->watchdog_timeo)))
|
|
|
|
return;
|
|
|
|
|
|
|
|
if (tx_ring) {
|
2018-10-26 10:41:00 -07:00
|
|
|
struct ice_hw *hw = &pf->hw;
|
|
|
|
u32 head, val = 0;
|
|
|
|
|
|
|
|
head = (rd32(hw, QTX_COMM_HEAD(vsi->txq_map[hung_queue])) &
|
|
|
|
QTX_COMM_HEAD_HEAD_M) >> QTX_COMM_HEAD_HEAD_S;
|
2018-08-09 06:29:53 -07:00
|
|
|
/* Read interrupt register */
|
|
|
|
if (test_bit(ICE_FLAG_MSIX_ENA, pf->flags))
|
2018-10-26 10:41:00 -07:00
|
|
|
val = rd32(hw,
|
2019-02-28 15:25:59 -08:00
|
|
|
GLINT_DYN_CTL(tx_ring->q_vector->reg_idx));
|
2018-08-09 06:29:53 -07:00
|
|
|
|
2018-10-26 10:41:00 -07:00
|
|
|
netdev_info(netdev, "tx_timeout: VSI_num: %d, Q %d, NTC: 0x%x, HW_HEAD: 0x%x, NTU: 0x%x, INT: 0x%x\n",
|
2018-08-09 06:29:53 -07:00
|
|
|
vsi->vsi_num, hung_queue, tx_ring->next_to_clean,
|
2018-10-26 10:41:00 -07:00
|
|
|
head, tx_ring->next_to_use, val);
|
2018-08-09 06:29:53 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
pf->tx_timeout_last_recovery = jiffies;
|
|
|
|
netdev_info(netdev, "tx_timeout recovery level %d, hung_queue %d\n",
|
|
|
|
pf->tx_timeout_recovery_level, hung_queue);
|
|
|
|
|
|
|
|
switch (pf->tx_timeout_recovery_level) {
|
|
|
|
case 1:
|
|
|
|
set_bit(__ICE_PFR_REQ, pf->state);
|
|
|
|
break;
|
|
|
|
case 2:
|
|
|
|
set_bit(__ICE_CORER_REQ, pf->state);
|
|
|
|
break;
|
|
|
|
case 3:
|
|
|
|
set_bit(__ICE_GLOBR_REQ, pf->state);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
netdev_err(netdev, "tx_timeout recovery unsuccessful, device is in unrecoverable state.\n");
|
|
|
|
set_bit(__ICE_DOWN, pf->state);
|
|
|
|
set_bit(__ICE_NEEDS_RESTART, vsi->state);
|
2018-08-09 06:29:57 -07:00
|
|
|
set_bit(__ICE_SERVICE_DIS, pf->state);
|
2018-08-09 06:29:53 -07:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
ice_service_task_schedule(pf);
|
|
|
|
pf->tx_timeout_recovery_level++;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:13 -07:00
|
|
|
/**
|
|
|
|
* ice_open - Called when a network interface becomes active
|
|
|
|
* @netdev: network interface device structure
|
|
|
|
*
|
|
|
|
* The open entry point is called when a network interface is made
|
2018-10-26 11:44:46 -07:00
|
|
|
* active by the system (IFF_UP). At this point all resources needed
|
2018-03-20 07:58:13 -07:00
|
|
|
* for transmit and receive operations are allocated, the interrupt
|
|
|
|
* handler is registered with the OS, the netdev watchdog is enabled,
|
|
|
|
* and the stack is notified that the interface is ready.
|
|
|
|
*
|
|
|
|
* Returns 0 on success, negative value on failure
|
|
|
|
*/
|
2019-04-16 10:30:43 -07:00
|
|
|
int ice_open(struct net_device *netdev)
|
2018-03-20 07:58:13 -07:00
|
|
|
{
|
|
|
|
struct ice_netdev_priv *np = netdev_priv(netdev);
|
|
|
|
struct ice_vsi *vsi = np->vsi;
|
|
|
|
int err;
|
|
|
|
|
2018-08-09 06:29:50 -07:00
|
|
|
if (test_bit(__ICE_NEEDS_RESTART, vsi->back->state)) {
|
|
|
|
netdev_err(netdev, "driver needs to be unloaded and reloaded\n");
|
|
|
|
return -EIO;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:13 -07:00
|
|
|
netif_carrier_off(netdev);
|
|
|
|
|
2018-12-19 10:03:25 -08:00
|
|
|
err = ice_force_phys_link_state(vsi, true);
|
|
|
|
if (err) {
|
|
|
|
netdev_err(netdev,
|
|
|
|
"Failed to set physical link up, error %d\n", err);
|
|
|
|
return err;
|
|
|
|
}
|
2018-03-20 07:58:13 -07:00
|
|
|
|
2018-12-19 10:03:25 -08:00
|
|
|
err = ice_vsi_open(vsi);
|
2018-03-20 07:58:13 -07:00
|
|
|
if (err)
|
|
|
|
netdev_err(netdev, "Failed to open VSI 0x%04X on switch 0x%04X\n",
|
|
|
|
vsi->vsi_num, vsi->vsw->sw_id);
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ice_stop - Disables a network interface
|
|
|
|
* @netdev: network interface device structure
|
|
|
|
*
|
|
|
|
* The stop entry point is called when an interface is de-activated by the OS,
|
2018-10-26 11:44:46 -07:00
|
|
|
* and the netdevice enters the DOWN state. The hardware is still under the
|
2018-03-20 07:58:13 -07:00
|
|
|
* driver's control, but the netdev interface is disabled.
|
|
|
|
*
|
|
|
|
* Returns success only - not allowed to fail
|
|
|
|
*/
|
2019-04-16 10:30:43 -07:00
|
|
|
int ice_stop(struct net_device *netdev)
|
2018-03-20 07:58:13 -07:00
|
|
|
{
|
|
|
|
struct ice_netdev_priv *np = netdev_priv(netdev);
|
|
|
|
struct ice_vsi *vsi = np->vsi;
|
|
|
|
|
|
|
|
ice_vsi_close(vsi);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:19 -07:00
|
|
|
/**
|
|
|
|
* ice_features_check - Validate encapsulated packet conforms to limits
|
|
|
|
* @skb: skb buffer
|
|
|
|
* @netdev: This port's netdev
|
|
|
|
* @features: Offload features that the stack believes apply
|
|
|
|
*/
|
|
|
|
static netdev_features_t
|
|
|
|
ice_features_check(struct sk_buff *skb,
|
|
|
|
struct net_device __always_unused *netdev,
|
|
|
|
netdev_features_t features)
|
|
|
|
{
|
|
|
|
size_t len;
|
|
|
|
|
|
|
|
/* No point in doing any of this if neither checksum nor GSO are
|
2018-10-26 11:44:46 -07:00
|
|
|
* being requested for this frame. We can rule out both by just
|
2018-03-20 07:58:19 -07:00
|
|
|
* checking for CHECKSUM_PARTIAL
|
|
|
|
*/
|
|
|
|
if (skb->ip_summed != CHECKSUM_PARTIAL)
|
|
|
|
return features;
|
|
|
|
|
|
|
|
/* We cannot support GSO if the MSS is going to be less than
|
2018-10-26 11:44:46 -07:00
|
|
|
* 64 bytes. If it is then we need to drop support for GSO.
|
2018-03-20 07:58:19 -07:00
|
|
|
*/
|
|
|
|
if (skb_is_gso(skb) && (skb_shinfo(skb)->gso_size < 64))
|
|
|
|
features &= ~NETIF_F_GSO_MASK;
|
|
|
|
|
|
|
|
len = skb_network_header(skb) - skb->data;
|
|
|
|
if (len & ~(ICE_TXD_MACLEN_MAX))
|
|
|
|
goto out_rm_features;
|
|
|
|
|
|
|
|
len = skb_transport_header(skb) - skb_network_header(skb);
|
|
|
|
if (len & ~(ICE_TXD_IPLEN_MAX))
|
|
|
|
goto out_rm_features;
|
|
|
|
|
|
|
|
if (skb->encapsulation) {
|
|
|
|
len = skb_inner_network_header(skb) - skb_transport_header(skb);
|
|
|
|
if (len & ~(ICE_TXD_L4LEN_MAX))
|
|
|
|
goto out_rm_features;
|
|
|
|
|
|
|
|
len = skb_inner_transport_header(skb) -
|
|
|
|
skb_inner_network_header(skb);
|
|
|
|
if (len & ~(ICE_TXD_IPLEN_MAX))
|
|
|
|
goto out_rm_features;
|
|
|
|
}
|
|
|
|
|
|
|
|
return features;
|
|
|
|
out_rm_features:
|
|
|
|
return features & ~(NETIF_F_CSUM_MASK | NETIF_F_GSO_MASK);
|
|
|
|
}
|
|
|
|
|
2018-03-20 07:58:13 -07:00
|
|
|
static const struct net_device_ops ice_netdev_ops = {
|
|
|
|
.ndo_open = ice_open,
|
|
|
|
.ndo_stop = ice_stop,
|
2018-03-20 07:58:14 -07:00
|
|
|
.ndo_start_xmit = ice_start_xmit,
|
2018-03-20 07:58:19 -07:00
|
|
|
.ndo_features_check = ice_features_check,
|
|
|
|
.ndo_set_rx_mode = ice_set_rx_mode,
|
|
|
|
.ndo_set_mac_address = ice_set_mac_address,
|
|
|
|
.ndo_validate_addr = eth_validate_addr,
|
|
|
|
.ndo_change_mtu = ice_change_mtu,
|
2018-03-20 07:58:16 -07:00
|
|
|
.ndo_get_stats64 = ice_get_stats64,
|
2018-09-19 17:42:58 -07:00
|
|
|
.ndo_set_vf_spoofchk = ice_set_vf_spoofchk,
|
|
|
|
.ndo_set_vf_mac = ice_set_vf_mac,
|
|
|
|
.ndo_get_vf_config = ice_get_vf_cfg,
|
|
|
|
.ndo_set_vf_trust = ice_set_vf_trust,
|
|
|
|
.ndo_set_vf_vlan = ice_set_vf_port_vlan,
|
|
|
|
.ndo_set_vf_link_state = ice_set_vf_link_state,
|
2018-03-20 07:58:15 -07:00
|
|
|
.ndo_vlan_rx_add_vid = ice_vlan_rx_add_vid,
|
|
|
|
.ndo_vlan_rx_kill_vid = ice_vlan_rx_kill_vid,
|
|
|
|
.ndo_set_features = ice_set_features,
|
2018-08-09 06:29:54 -07:00
|
|
|
.ndo_bridge_getlink = ice_bridge_getlink,
|
|
|
|
.ndo_bridge_setlink = ice_bridge_setlink,
|
2018-03-20 07:58:19 -07:00
|
|
|
.ndo_fdb_add = ice_fdb_add,
|
|
|
|
.ndo_fdb_del = ice_fdb_del,
|
2018-08-09 06:29:53 -07:00
|
|
|
.ndo_tx_timeout = ice_tx_timeout,
|
2018-03-20 07:58:13 -07:00
|
|
|
};
|