d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
e5d179078b
numam-dpdk/drivers/net/bnxt/bnxt_cpr.c

354 lines
9.4 KiB
C
Raw Normal View History

net/bnxt: convert to SPDX license tag Update the license header on bnxt files to be the standard BSD-3-Clause license used for the rest of DPDK, bring the files in compliance with the DPDK licensing policy. Signed-off-by: Scott Branden <scott.branden@broadcom.com> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2018-04-02 22:34:32 +00:00
/* SPDX-License-Identifier: BSD-3-Clause
* Copyright(c) 2014-2018 Broadcom
* All rights reserved.
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
*/
net/bnxt: allocate Rx/Tx and completion rings Perform allocation and free()ing of ring and information structures for the TX, RX, and completion rings. The previous patches had so far provided top level stubs and generic ring support, while this patch does the real allocation and freeing of the memory specific to each different type of generic ring. For example bnxt_init_tx_ring_struct() or bnxt_init_rx_ring_struct() is now allocating memory based on the socked_id being provided. bnxt_tx_queue_setup_op() or bnxt_rx_queue_setup_op() have gone through some reformatting to perform a graceful cleanup in case memory allocation fails. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:15 +00:00
#include <rte_malloc.h>
net/bnxt: handle reset notify async event from FW When the FW upgrade is initiated the current instance of FW issues a HWRM_ASYNC_EVENT_CMPL_EVENT_ID_RESET_NOTIFY async notification to the driver. On receiving this notification, the PMD shall quiesce itself and poll on the HWRM_VER_GET FW command at regular intervals. Once the VER_GET command succeeds, the driver should go through the rediscovery process and re-initialize the device. Also register with FW for the reset notify async event. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2019-10-02 01:23:23 +00:00
#include <rte_alarm.h>
net/bnxt: support hot firmware upgrade for Stingray FW sets HWRM_FUNC_QCAPS_OUTPUT_FLAGS_ERR_RECOVER_RELOAD in HWRM_FUNC_QCAPS command, if device requires to invoke fastboot FW during FW reset. Driver has to poll for shutdown bit in fw_status register: 1. in case of hot fw upgrade, this bit will be set after all function drivers unregistered with fw. 2. in case of fw initiated error recovery, this bit will be set after fw has collected the core dump Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Signed-off-by: Rahul Gupta <rahul.gupta@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2019-10-02 01:23:31 +00:00
#include <rte_cycles.h>
net/bnxt: allocate Rx/Tx and completion rings Perform allocation and free()ing of ring and information structures for the TX, RX, and completion rings. The previous patches had so far provided top level stubs and generic ring support, while this patch does the real allocation and freeing of the memory specific to each different type of generic ring. For example bnxt_init_tx_ring_struct() or bnxt_init_rx_ring_struct() is now allocating memory based on the socked_id being provided. bnxt_tx_queue_setup_op() or bnxt_rx_queue_setup_op() have gone through some reformatting to perform a graceful cleanup in case memory allocation fails. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:15 +00:00
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
#include "bnxt.h"
#include "bnxt_hwrm.h"
#include "bnxt_ring.h"
net/bnxt: add statistics Add the bnxt_stats_get_op() and bnxt_stats_reset_op() dev_ops to get and reset statistics. It also brings in the associated HWRM calls to handle the requests appropriately. We also have the bnxt_free_stats() function which will be used in the follow on patches to free the memory allocated by the driver for statistics. New HWRM calls: bnxt_hwrm_stat_clear: This command clears statistics of a context Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:12 +00:00
#include "hsi_struct_def_dpdk.h"
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
net/bnxt: support hot firmware upgrade for Stingray FW sets HWRM_FUNC_QCAPS_OUTPUT_FLAGS_ERR_RECOVER_RELOAD in HWRM_FUNC_QCAPS command, if device requires to invoke fastboot FW during FW reset. Driver has to poll for shutdown bit in fw_status register: 1. in case of hot fw upgrade, this bit will be set after all function drivers unregistered with fw. 2. in case of fw initiated error recovery, this bit will be set after fw has collected the core dump Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Signed-off-by: Rahul Gupta <rahul.gupta@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2019-10-02 01:23:31 +00:00
void bnxt_wait_for_device_shutdown(struct bnxt *bp)
{
uint32_t val, timeout;
/* if HWRM_FUNC_QCAPS_OUTPUT_FLAGS_ERR_RECOVER_RELOAD is set
* in HWRM_FUNC_QCAPS command, wait for FW_STATUS to set
* the SHUTDOWN bit in health register
*/
if (!(bp->recovery_info &&
net/bnxt: add a field for FW capabilities The purpose of this patch is used to add a new field "fw_cap" in bnxt structure. The new "fw_cap" field store all the capabilities reported by the FW. This information will help us to determine the device capabilities when registering feature support with FW. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2019-12-10 15:05:29 +00:00
(bp->fw_cap & BNXT_FW_CAP_ERR_RECOVER_RELOAD)))
net/bnxt: support hot firmware upgrade for Stingray FW sets HWRM_FUNC_QCAPS_OUTPUT_FLAGS_ERR_RECOVER_RELOAD in HWRM_FUNC_QCAPS command, if device requires to invoke fastboot FW during FW reset. Driver has to poll for shutdown bit in fw_status register: 1. in case of hot fw upgrade, this bit will be set after all function drivers unregistered with fw. 2. in case of fw initiated error recovery, this bit will be set after fw has collected the core dump Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Signed-off-by: Rahul Gupta <rahul.gupta@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2019-10-02 01:23:31 +00:00
return;
/* Driver has to wait for fw_reset_max_msecs or shutdown bit which comes
* first for FW to collect crash dump.
*/
timeout = bp->fw_reset_max_msecs;
/* Driver has to poll for shutdown bit in fw_status register
*
* 1. in case of hot fw upgrade, this bit will be set after all
* function drivers unregistered with fw.
* 2. in case of fw initiated error recovery, this bit will be
* set after fw has collected the core dump
*/
do {
val = bnxt_read_fw_status_reg(bp, BNXT_FW_STATUS_REG);
if (val & BNXT_FW_STATUS_SHUTDOWN)
return;
rte_delay_ms(100);
timeout -= 100;
} while (timeout);
}
net/bnxt: fix VF representor port add Fix VF representor port add when it's endpoint interface is down. While adding vf representor port to a bridge, vnic & svif information of vf representors endpoint(VF) would be needed to program default flow rules. However, if the endpoint interface is down when vf representor port is added, firmware will return invalid vnic & svif information. This patch fixes the problem by registering to DEFAULT_VNIC_CHANGE async event and once the async event is received, use the endpoint information(VF's fid) to fetch it's vnic & svif information and program the default flow rules. Fixes: 322bd6e70272 ("net/bnxt: add port representor infrastructure") Cc: stable@dpdk.org Signed-off-by: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-07-29 14:04:59 +00:00
static void
bnxt_process_default_vnic_change(struct bnxt *bp,
struct hwrm_async_event_cmpl *async_cmp)
{
net/bnxt: handle default VNIC change async event Currently, we are only registering to this event if the function is a trusted VF. This patch extends it for PFs as well. Fixes: 322bd6e70272 ("net/bnxt: add port representor infrastructure") Cc: stable@dpdk.org Signed-off-by: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-10-09 11:11:24 +00:00
uint16_t vnic_state, vf_fid, vf_id;
net/bnxt: support representors on remote host domain In the Stingray use case, representors are conventionally run inside the SoC domain representing functions that are on the X86 domain. In order to support this mechanism of building representors for endpoints that are not in the same host domain, additional dev args have been in the PMD like so: rep-based-pf=<physical index> rep-is-pf=<VF=0 or PF=1> where `rep-based-pf` specifies the physical index of the base PF that the representor is derived off of. Since representor(s) can be created for endpoint PFs as well, rename struct bnxt_vf_representor to bnxt_representor and other such dev_ops and function names. devargs have also been extended to specify the exact CoS queue along with flow control enablement to be used for the conduit between the representor and the endpoint function. This is how a sample devargs would look with all the extended devargs -w 0000:06:02.0,host-based-truflow=1,representor=[1],rep-based-pf=8, rep-is-pf=1,rep-q-r2f=1,rep-fc-r2f=0,rep-q-f2r=1,rep-fc-f2r=1 Call CFA_PAIR_ALLOC only in case of Stingray instead of CFA_VFR_ALLOC. Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Mike Baucom <michael.baucom@broadcom.com> Reviewed-by: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-09-22 07:06:30 +00:00
struct bnxt_representor *vf_rep_bp;
net/bnxt: fix VF representor port add Fix VF representor port add when it's endpoint interface is down. While adding vf representor port to a bridge, vnic & svif information of vf representors endpoint(VF) would be needed to program default flow rules. However, if the endpoint interface is down when vf representor port is added, firmware will return invalid vnic & svif information. This patch fixes the problem by registering to DEFAULT_VNIC_CHANGE async event and once the async event is received, use the endpoint information(VF's fid) to fetch it's vnic & svif information and program the default flow rules. Fixes: 322bd6e70272 ("net/bnxt: add port representor infrastructure") Cc: stable@dpdk.org Signed-off-by: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-07-29 14:04:59 +00:00
struct rte_eth_dev *eth_dev;
bool vfr_found = false;
uint32_t event_data;
if (!BNXT_TRUFLOW_EN(bp))
return;
PMD_DRV_LOG(INFO, "Default vnic change async event received\n");
event_data = rte_le_to_cpu_32(async_cmp->event_data1);
vnic_state = (event_data & BNXT_DEFAULT_VNIC_STATE_MASK) >>
BNXT_DEFAULT_VNIC_STATE_SFT;
if (vnic_state != BNXT_DEFAULT_VNIC_ALLOC)
return;
net/bnxt: handle default VNIC change async event Currently, we are only registering to this event if the function is a trusted VF. This patch extends it for PFs as well. Fixes: 322bd6e70272 ("net/bnxt: add port representor infrastructure") Cc: stable@dpdk.org Signed-off-by: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-10-09 11:11:24 +00:00
if (!bp->rep_info)
net/bnxt: fix VF representor port add Fix VF representor port add when it's endpoint interface is down. While adding vf representor port to a bridge, vnic & svif information of vf representors endpoint(VF) would be needed to program default flow rules. However, if the endpoint interface is down when vf representor port is added, firmware will return invalid vnic & svif information. This patch fixes the problem by registering to DEFAULT_VNIC_CHANGE async event and once the async event is received, use the endpoint information(VF's fid) to fetch it's vnic & svif information and program the default flow rules. Fixes: 322bd6e70272 ("net/bnxt: add port representor infrastructure") Cc: stable@dpdk.org Signed-off-by: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-07-29 14:04:59 +00:00
return;
vf_fid = (event_data & BNXT_DEFAULT_VNIC_CHANGE_VF_ID_MASK) >>
BNXT_DEFAULT_VNIC_CHANGE_VF_ID_SFT;
PMD_DRV_LOG(INFO, "async event received vf_id 0x%x\n", vf_fid);
for (vf_id = 0; vf_id < BNXT_MAX_VF_REPS; vf_id++) {
eth_dev = bp->rep_info[vf_id].vfr_eth_dev;
if (!eth_dev)
continue;
vf_rep_bp = eth_dev->data->dev_private;
if (vf_rep_bp &&
vf_rep_bp->fw_fid == vf_fid) {
vfr_found = true;
break;
}
}
if (!vfr_found)
return;
net/bnxt: support representors on remote host domain In the Stingray use case, representors are conventionally run inside the SoC domain representing functions that are on the X86 domain. In order to support this mechanism of building representors for endpoints that are not in the same host domain, additional dev args have been in the PMD like so: rep-based-pf=<physical index> rep-is-pf=<VF=0 or PF=1> where `rep-based-pf` specifies the physical index of the base PF that the representor is derived off of. Since representor(s) can be created for endpoint PFs as well, rename struct bnxt_vf_representor to bnxt_representor and other such dev_ops and function names. devargs have also been extended to specify the exact CoS queue along with flow control enablement to be used for the conduit between the representor and the endpoint function. This is how a sample devargs would look with all the extended devargs -w 0000:06:02.0,host-based-truflow=1,representor=[1],rep-based-pf=8, rep-is-pf=1,rep-q-r2f=1,rep-fc-r2f=0,rep-q-f2r=1,rep-fc-f2r=1 Call CFA_PAIR_ALLOC only in case of Stingray instead of CFA_VFR_ALLOC. Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Mike Baucom <michael.baucom@broadcom.com> Reviewed-by: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-09-22 07:06:30 +00:00
bnxt_rep_dev_start_op(eth_dev);
net/bnxt: fix VF representor port add Fix VF representor port add when it's endpoint interface is down. While adding vf representor port to a bridge, vnic & svif information of vf representors endpoint(VF) would be needed to program default flow rules. However, if the endpoint interface is down when vf representor port is added, firmware will return invalid vnic & svif information. This patch fixes the problem by registering to DEFAULT_VNIC_CHANGE async event and once the async event is received, use the endpoint information(VF's fid) to fetch it's vnic & svif information and program the default flow rules. Fixes: 322bd6e70272 ("net/bnxt: add port representor infrastructure") Cc: stable@dpdk.org Signed-off-by: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-07-29 14:04:59 +00:00
}
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
/*
* Async event handling
*/
net/bnxt: support async link notification This patch adds support to get Link notification asynchronously. The HW sends async notifications on default completion ring. The PMD processes these notifications and logs a message appropriately. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2016-10-11 21:47:50 +00:00
void bnxt_handle_async_event(struct bnxt *bp,
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
struct cmpl_base *cmp)
{
struct hwrm_async_event_cmpl *async_cmp =
(struct hwrm_async_event_cmpl *)cmp;
net/bnxt: support async link notification This patch adds support to get Link notification asynchronously. The HW sends async notifications on default completion ring. The PMD processes these notifications and logs a message appropriately. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2016-10-11 21:47:50 +00:00
uint16_t event_id = rte_le_to_cpu_16(async_cmp->event_id);
net/bnxt: handle error recovery FW event 1. Advertise HWRM_FUNC_DRV_RGTR_INPUT_FLAGS_ERROR_RECOVERY_SUPPORT flag in the FUNC_DRV_RGTR command. 2. request for the async event ASYNC_EVENT_CMPL_EVENT_ID_ERROR_RECOVERY in the FUNC_DRV_RGTR command. 3. handle the async event EVENT_ID_ERROR_RECOVERY from FW. Error recovery support will be used by firmware only if all the driver instances support error recovery process. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2019-10-02 01:23:28 +00:00
struct bnxt_error_recovery_info *info;
net/bnxt: handle fatal event from FW When firmware hit some unrecoverable error conditions, firmware initiate the recovery by sending an async event EVENT_CMPL_EVENT_ID_RESET_NOTIFY with data1 set to RESET_NOTIFY_EVENT_DATA1_REASON_CODE_FW_EXCEPTION_FATAL to all host drivers and will reset the chip. The recovery procedure is same sequence as the one for hot FW upgrade. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2019-10-02 01:23:25 +00:00
uint32_t event_data;
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
net/bnxt: support async link notification This patch adds support to get Link notification asynchronously. The HW sends async notifications on default completion ring. The PMD processes these notifications and logs a message appropriately. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2016-10-11 21:47:50 +00:00
switch (event_id) {
case HWRM_ASYNC_EVENT_CMPL_EVENT_ID_LINK_STATUS_CHANGE:
case HWRM_ASYNC_EVENT_CMPL_EVENT_ID_LINK_SPEED_CHANGE:
case HWRM_ASYNC_EVENT_CMPL_EVENT_ID_LINK_SPEED_CFG_CHANGE:
net/bnxt: add fallthrough comment The FALLTHROUGH comment for cascading switch cases was missing in a few places. This patch adds that. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2018-05-22 18:13:41 +00:00
/* FALLTHROUGH */
net/bnxt: fix link update 1. When port is stopped, we can forcibly set the link status for the device to down. 2. VFs and MH PFs do not have the privilege to bring the link down. As a result driver prints "Link Up" when port is stopped. 3. When driver receives link status/speed/config async event from fw, driver invokes bnxt_link_update() with exp_link_status as ETH_LINK_UP This is not logically correct as the async event could be for Link up or link down or for speed change. Fixes: 074cacb9907a ("net/bnxt: fix link during port toggle") Cc: stable@dpdk.org Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-10-06 16:01:56 +00:00
bnxt_link_update_op(bp->eth_dev, 0);
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
break;
net/bnxt: register for more async events Register for async events from the FW. New events we are registering for include Link speed config changes, PF driver unload and VF config change. Also log a message when the async event arrives on the completion ring. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2018-01-26 17:31:56 +00:00
case HWRM_ASYNC_EVENT_CMPL_EVENT_ID_PF_DRVR_UNLOAD:
PMD_DRV_LOG(INFO, "Async event: PF driver unloaded\n");
break;
case HWRM_ASYNC_EVENT_CMPL_EVENT_ID_VF_CFG_CHANGE:
PMD_DRV_LOG(INFO, "Async event: VF config changed\n");
net/bnxt: use configured MTU during load The MTU value of a port can be (re)configured out-of-band. FW will be returning this configured MTU as part of func_qcfg cmd. Driver to use this value during load time. Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Lance Richardson <lance.richardson@broadcom.com> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2019-06-08 19:22:05 +00:00
bnxt_hwrm_func_qcfg(bp, NULL);
net/bnxt: register for more async events Register for async events from the FW. New events we are registering for include Link speed config changes, PF driver unload and VF config change. Also log a message when the async event arrives on the completion ring. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2018-01-26 17:31:56 +00:00
break;
case HWRM_ASYNC_EVENT_CMPL_EVENT_ID_PORT_CONN_NOT_ALLOWED:
PMD_DRV_LOG(INFO, "Port conn async event\n");
break;
net/bnxt: handle reset notify async event from FW When the FW upgrade is initiated the current instance of FW issues a HWRM_ASYNC_EVENT_CMPL_EVENT_ID_RESET_NOTIFY async notification to the driver. On receiving this notification, the PMD shall quiesce itself and poll on the HWRM_VER_GET FW command at regular intervals. Once the VER_GET command succeeds, the driver should go through the rediscovery process and re-initialize the device. Also register with FW for the reset notify async event. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2019-10-02 01:23:23 +00:00
case HWRM_ASYNC_EVENT_CMPL_EVENT_ID_RESET_NOTIFY:
net/bnxt: fix Rx performance by removing spinlock The spinlock was trying to protect scenarios where rx_queue stop/start could be initiated dynamically. Assigning bnxt_dummy_recv_pkts and bnxt_dummy_xmit_pkts immediately to avoid concurrent access of mbuf in Rx and cleanup path should help achieve the same result. Fixes: 14255b351537 ("net/bnxt: fix queue start/stop operations") Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Signed-off-by: Rahul Gupta <rahul.gupta@broadcom.com>
2020-10-26 03:56:16 +00:00
/*
* Avoid any rx/tx packet processing during firmware reset
* operation.
*/
bnxt_stop_rxtx(bp);
net/bnxt: fix race condition when port is stopped Fix a race condition between port stop and error recovery task. When io forwarding is not started on Stingray devices, driver will not receive the async event from FW when there is a FW reset. While exiting testpmd, as part of port stop driver sees this event and this in turn causes a race between port stop and error recovery task. Fixed this by ignoring the fatal/non-fatal async event from FW while stopping port. Fixes: df6cd7c1f73a ("net/bnxt: handle reset notify async event from FW") Cc: stable@dpdk.org Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Rahul Gupta <rahul.gupta@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-02-20 04:12:14 +00:00
/* Ignore reset notify async events when stopping the port */
if (!bp->eth_dev->data->dev_started) {
bp->flags |= BNXT_FLAG_FATAL_ERROR;
return;
}
net/bnxt: check chip reset in stop and close While the error recovery thread is running, an application can invoke dev_stop or dev_close_op thus triggering a race and unwanted consequences if dev_close is invoked while the recovery is not yet completed. Fix by having another lock to synchronize between the 2 threads and return EGAIN if adapter is in the middle of recovery when dev_stop or dev_close ops are invoked Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-12-24 09:37:34 +00:00
pthread_mutex_lock(&bp->err_recovery_lock);
net/bnxt: handle fatal event from FW When firmware hit some unrecoverable error conditions, firmware initiate the recovery by sending an async event EVENT_CMPL_EVENT_ID_RESET_NOTIFY with data1 set to RESET_NOTIFY_EVENT_DATA1_REASON_CODE_FW_EXCEPTION_FATAL to all host drivers and will reset the chip. The recovery procedure is same sequence as the one for hot FW upgrade. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2019-10-02 01:23:25 +00:00
event_data = rte_le_to_cpu_32(async_cmp->event_data1);
net/bnxt: handle reset notify async event from FW When the FW upgrade is initiated the current instance of FW issues a HWRM_ASYNC_EVENT_CMPL_EVENT_ID_RESET_NOTIFY async notification to the driver. On receiving this notification, the PMD shall quiesce itself and poll on the HWRM_VER_GET FW command at regular intervals. Once the VER_GET command succeeds, the driver should go through the rediscovery process and re-initialize the device. Also register with FW for the reset notify async event. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2019-10-02 01:23:23 +00:00
/* timestamp_lo/hi values are in units of 100ms */
bp->fw_reset_max_msecs = async_cmp->timestamp_hi ?
rte_le_to_cpu_16(async_cmp->timestamp_hi) * 100 :
BNXT_MAX_FW_RESET_TIMEOUT;
bp->fw_reset_min_msecs = async_cmp->timestamp_lo ?
async_cmp->timestamp_lo * 100 :
BNXT_MIN_FW_READY_TIMEOUT;
net/bnxt: handle fatal event from FW When firmware hit some unrecoverable error conditions, firmware initiate the recovery by sending an async event EVENT_CMPL_EVENT_ID_RESET_NOTIFY with data1 set to RESET_NOTIFY_EVENT_DATA1_REASON_CODE_FW_EXCEPTION_FATAL to all host drivers and will reset the chip. The recovery procedure is same sequence as the one for hot FW upgrade. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2019-10-02 01:23:25 +00:00
if ((event_data & EVENT_DATA1_REASON_CODE_MASK) ==
EVENT_DATA1_REASON_CODE_FW_EXCEPTION_FATAL) {
PMD_DRV_LOG(INFO,
"Firmware fatal reset event received\n");
bp->flags |= BNXT_FLAG_FATAL_ERROR;
} else {
PMD_DRV_LOG(INFO,
"Firmware non-fatal reset event received\n");
}
net/bnxt: handle reset notify async event from FW When the FW upgrade is initiated the current instance of FW issues a HWRM_ASYNC_EVENT_CMPL_EVENT_ID_RESET_NOTIFY async notification to the driver. On receiving this notification, the PMD shall quiesce itself and poll on the HWRM_VER_GET FW command at regular intervals. Once the VER_GET command succeeds, the driver should go through the rediscovery process and re-initialize the device. Also register with FW for the reset notify async event. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2019-10-02 01:23:23 +00:00
bp->flags |= BNXT_FLAG_FW_RESET;
net/bnxt: check chip reset in stop and close While the error recovery thread is running, an application can invoke dev_stop or dev_close_op thus triggering a race and unwanted consequences if dev_close is invoked while the recovery is not yet completed. Fix by having another lock to synchronize between the 2 threads and return EGAIN if adapter is in the middle of recovery when dev_stop or dev_close ops are invoked Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-12-24 09:37:34 +00:00
pthread_mutex_unlock(&bp->err_recovery_lock);
net/bnxt: handle reset notify async event from FW When the FW upgrade is initiated the current instance of FW issues a HWRM_ASYNC_EVENT_CMPL_EVENT_ID_RESET_NOTIFY async notification to the driver. On receiving this notification, the PMD shall quiesce itself and poll on the HWRM_VER_GET FW command at regular intervals. Once the VER_GET command succeeds, the driver should go through the rediscovery process and re-initialize the device. Also register with FW for the reset notify async event. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2019-10-02 01:23:23 +00:00
rte_eal_alarm_set(US_PER_MS, bnxt_dev_reset_and_resume,
(void *)bp);
break;
net/bnxt: handle error recovery FW event 1. Advertise HWRM_FUNC_DRV_RGTR_INPUT_FLAGS_ERROR_RECOVERY_SUPPORT flag in the FUNC_DRV_RGTR command. 2. request for the async event ASYNC_EVENT_CMPL_EVENT_ID_ERROR_RECOVERY in the FUNC_DRV_RGTR command. 3. handle the async event EVENT_ID_ERROR_RECOVERY from FW. Error recovery support will be used by firmware only if all the driver instances support error recovery process. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2019-10-02 01:23:28 +00:00
case HWRM_ASYNC_EVENT_CMPL_EVENT_ID_ERROR_RECOVERY:
info = bp->recovery_info;
if (!info)
return;
PMD_DRV_LOG(INFO, "Error recovery async event received\n");
event_data = rte_le_to_cpu_32(async_cmp->event_data1) &
EVENT_DATA1_FLAGS_MASK;
if (event_data & EVENT_DATA1_FLAGS_MASTER_FUNC)
info->flags |= BNXT_FLAG_MASTER_FUNC;
else
info->flags &= ~BNXT_FLAG_MASTER_FUNC;
if (event_data & EVENT_DATA1_FLAGS_RECOVERY_ENABLED)
info->flags |= BNXT_FLAG_RECOVERY_ENABLED;
else
info->flags &= ~BNXT_FLAG_RECOVERY_ENABLED;
PMD_DRV_LOG(INFO, "recovery enabled(%d), master function(%d)\n",
bnxt_is_recovery_enabled(bp),
bnxt_is_master_func(bp));
net/bnxt: support periodic FW health monitoring Periodically poll the FW heartbeat register and FW recovery counter registers to check the FW health. Polling frequency will be advertised by the FW in HWRM_ERROR_RECOVERY_QCFG response. Schedule the task upon receiving the async event from FW. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2019-10-02 01:23:29 +00:00
if (bp->flags & BNXT_FLAG_FW_HEALTH_CHECK_SCHEDULED)
return;
info->last_heart_beat =
bnxt_read_fw_status_reg(bp, BNXT_FW_HEARTBEAT_CNT_REG);
info->last_reset_counter =
bnxt_read_fw_status_reg(bp, BNXT_FW_RECOVERY_CNT_REG);
bnxt_schedule_fw_health_check(bp);
net/bnxt: handle error recovery FW event 1. Advertise HWRM_FUNC_DRV_RGTR_INPUT_FLAGS_ERROR_RECOVERY_SUPPORT flag in the FUNC_DRV_RGTR command. 2. request for the async event ASYNC_EVENT_CMPL_EVENT_ID_ERROR_RECOVERY in the FUNC_DRV_RGTR command. 3. handle the async event EVENT_ID_ERROR_RECOVERY from FW. Error recovery support will be used by firmware only if all the driver instances support error recovery process. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2019-10-02 01:23:28 +00:00
break;
net/bnxt: log firmware debug notifications The debug notifications are not functional in nature, they should only have diagnostic value. Other than logging to system log, drivers shall not take any other functional action based on this async event. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-02-06 16:33:10 +00:00
case HWRM_ASYNC_EVENT_CMPL_EVENT_ID_DEBUG_NOTIFICATION:
PMD_DRV_LOG(INFO, "DNC event: evt_data1 %#x evt_data2 %#x\n",
rte_le_to_cpu_32(async_cmp->event_data1),
rte_le_to_cpu_32(async_cmp->event_data2));
break;
net/bnxt: fix VF representor port add Fix VF representor port add when it's endpoint interface is down. While adding vf representor port to a bridge, vnic & svif information of vf representors endpoint(VF) would be needed to program default flow rules. However, if the endpoint interface is down when vf representor port is added, firmware will return invalid vnic & svif information. This patch fixes the problem by registering to DEFAULT_VNIC_CHANGE async event and once the async event is received, use the endpoint information(VF's fid) to fetch it's vnic & svif information and program the default flow rules. Fixes: 322bd6e70272 ("net/bnxt: add port representor infrastructure") Cc: stable@dpdk.org Signed-off-by: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-07-29 14:04:59 +00:00
case HWRM_ASYNC_EVENT_CMPL_EVENT_ID_DEFAULT_VNIC_CHANGE:
bnxt_process_default_vnic_change(bp, async_cmp);
break;
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
default:
net/bnxt: reduce verbosity of logs When IOMMU is available, EAL picks IOVA as VA as the default IOVA mode. This causes the bnxt driver to log warning messages saying "Memzone physical address same as virtual." and "Using rte_mem_virt2iova()" during load. Reduce the verbosity of logs to DEBUG. Reduced couple of other logs level to DEBUG as well. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Lance Richardson <lance.richardson@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2019-10-02 01:23:32 +00:00
PMD_DRV_LOG(DEBUG, "handle_async_event id = 0x%x\n", event_id);
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
break;
}
}
void bnxt_handle_fwd_req(struct bnxt *bp, struct cmpl_base *cmpl)
{
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
struct hwrm_exec_fwd_resp_input *fwreq;
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
struct hwrm_fwd_req_cmpl *fwd_cmpl = (struct hwrm_fwd_req_cmpl *)cmpl;
struct input *fwd_cmd;
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
uint16_t fw_vf_id;
uint16_t vf_id;
uint16_t req_len;
int rc;
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
net/bnxt: fix allocation of PF info struct Fixes: 804e746c7b73 ("net/bnxt: add hardware resource manager init code") Cc: stable@dpdk.org Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2020-05-15 11:10:41 +00:00
if (bp->pf->active_vfs <= 0) {
net/bnxt: use dynamic log type This patch implements driver specific log type doing away with usage of RTE_LOG() for logging. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2018-01-26 17:31:55 +00:00
PMD_DRV_LOG(ERR, "Forwarded VF with no active VFs\n");
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
return;
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
}
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
/* Qualify the fwd request */
fw_vf_id = rte_le_to_cpu_16(fwd_cmpl->source_id);
net/bnxt: fix allocation of PF info struct Fixes: 804e746c7b73 ("net/bnxt: add hardware resource manager init code") Cc: stable@dpdk.org Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2020-05-15 11:10:41 +00:00
vf_id = fw_vf_id - bp->pf->first_vf_id;
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
req_len = (rte_le_to_cpu_16(fwd_cmpl->req_len_type) &
HWRM_FWD_REQ_CMPL_REQ_LEN_MASK) >>
HWRM_FWD_REQ_CMPL_REQ_LEN_SFT;
if (req_len > sizeof(fwreq->encap_request))
req_len = sizeof(fwreq->encap_request);
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
/* Locate VF's forwarded command */
net/bnxt: fix allocation of PF info struct Fixes: 804e746c7b73 ("net/bnxt: add hardware resource manager init code") Cc: stable@dpdk.org Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2020-05-15 11:10:41 +00:00
fwd_cmd = (struct input *)bp->pf->vf_info[vf_id].req_buf;
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
net/bnxt: fix allocation of PF info struct Fixes: 804e746c7b73 ("net/bnxt: add hardware resource manager init code") Cc: stable@dpdk.org Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2020-05-15 11:10:41 +00:00
if (fw_vf_id < bp->pf->first_vf_id ||
fw_vf_id >= bp->pf->first_vf_id + bp->pf->active_vfs) {
net/bnxt: use dynamic log type This patch implements driver specific log type doing away with usage of RTE_LOG() for logging. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2018-01-26 17:31:55 +00:00
PMD_DRV_LOG(ERR,
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
"FWD req's source_id 0x%x out of range 0x%x - 0x%x (%d %d)\n",
net/bnxt: fix allocation of PF info struct Fixes: 804e746c7b73 ("net/bnxt: add hardware resource manager init code") Cc: stable@dpdk.org Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2020-05-15 11:10:41 +00:00
fw_vf_id, bp->pf->first_vf_id,
(bp->pf->first_vf_id) + bp->pf->active_vfs - 1,
bp->pf->first_vf_id, bp->pf->active_vfs);
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
goto reject;
}
net/bnxt: fix PF support in SR-IOV mode 1. Implement HWRM_FUNC_VF_RESOURCE_CFG command and use it to reserve resources for VFs when NEW RM is enabled. 2. Invoke PF’s FUNC_CFG before configuring VFs resources. 3. Don’t consider max_rx_em_flows in max_l2_ctx calculation when VFs are configured. 4. Issue HWRM_FUNC_QCFG instead of HWRM_FUNC_QCAPS to find out the actual allocated resources for VF. 5. Don’t add random mac to the VF. 6. Handle completion type CMPL_BASE_TYPE_HWRM_FWD_REQ instead of CMPL_BASE_TYPE_HWRM_FWD_RESP. 7. Don't enable HWRM_FUNC_DRV_RGTR_INPUT_FLAGS_FWD_NONE_MODE when the list of HWRM commands that needs to be forwarded to the PF is specified in HWRM_FUNC_DRV_RGTR. 8. Update the HWRM commands list that can be forwarded to the PF. Fixes: b7778e8a1c00 ("net/bnxt: refactor to properly allocate resources for PF/VF") Cc: stable@dpdk.org Signed-off-by: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-10-09 11:11:21 +00:00
if (bnxt_rcv_msg_from_vf(bp, vf_id, fwd_cmd)) {
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
/*
* In older firmware versions, the MAC had to be all zeros for
* the VF to set it's MAC via hwrm_func_vf_cfg. Set to all
* zeros if it's being configured and has been ok'd by caller.
*/
if (fwd_cmd->req_type == HWRM_FUNC_VF_CFG) {
struct hwrm_func_vf_cfg_input *vfc = (void *)fwd_cmd;
if (vfc->enables &
HWRM_FUNC_VF_CFG_INPUT_ENABLES_DFLT_MAC_ADDR) {
bnxt_hwrm_func_vf_mac(bp, vf_id,
(const uint8_t *)"\x00\x00\x00\x00\x00");
}
}
net/bnxt: fix PF support in SR-IOV mode 1. Implement HWRM_FUNC_VF_RESOURCE_CFG command and use it to reserve resources for VFs when NEW RM is enabled. 2. Invoke PF’s FUNC_CFG before configuring VFs resources. 3. Don’t consider max_rx_em_flows in max_l2_ctx calculation when VFs are configured. 4. Issue HWRM_FUNC_QCFG instead of HWRM_FUNC_QCAPS to find out the actual allocated resources for VF. 5. Don’t add random mac to the VF. 6. Handle completion type CMPL_BASE_TYPE_HWRM_FWD_REQ instead of CMPL_BASE_TYPE_HWRM_FWD_RESP. 7. Don't enable HWRM_FUNC_DRV_RGTR_INPUT_FLAGS_FWD_NONE_MODE when the list of HWRM commands that needs to be forwarded to the PF is specified in HWRM_FUNC_DRV_RGTR. 8. Update the HWRM commands list that can be forwarded to the PF. Fixes: b7778e8a1c00 ("net/bnxt: refactor to properly allocate resources for PF/VF") Cc: stable@dpdk.org Signed-off-by: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-10-09 11:11:21 +00:00
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
if (fwd_cmd->req_type == HWRM_CFA_L2_SET_RX_MASK) {
struct hwrm_cfa_l2_set_rx_mask_input *srm =
(void *)fwd_cmd;
srm->vlan_tag_tbl_addr = rte_cpu_to_le_64(0);
srm->num_vlan_tags = rte_cpu_to_le_32(0);
srm->mask &= ~rte_cpu_to_le_32(
HWRM_CFA_L2_SET_RX_MASK_INPUT_MASK_VLANONLY |
HWRM_CFA_L2_SET_RX_MASK_INPUT_MASK_VLAN_NONVLAN |
HWRM_CFA_L2_SET_RX_MASK_INPUT_MASK_ANYVLAN_NONVLAN);
}
net/bnxt: fix PF support in SR-IOV mode 1. Implement HWRM_FUNC_VF_RESOURCE_CFG command and use it to reserve resources for VFs when NEW RM is enabled. 2. Invoke PF’s FUNC_CFG before configuring VFs resources. 3. Don’t consider max_rx_em_flows in max_l2_ctx calculation when VFs are configured. 4. Issue HWRM_FUNC_QCFG instead of HWRM_FUNC_QCAPS to find out the actual allocated resources for VF. 5. Don’t add random mac to the VF. 6. Handle completion type CMPL_BASE_TYPE_HWRM_FWD_REQ instead of CMPL_BASE_TYPE_HWRM_FWD_RESP. 7. Don't enable HWRM_FUNC_DRV_RGTR_INPUT_FLAGS_FWD_NONE_MODE when the list of HWRM commands that needs to be forwarded to the PF is specified in HWRM_FUNC_DRV_RGTR. 8. Update the HWRM commands list that can be forwarded to the PF. Fixes: b7778e8a1c00 ("net/bnxt: refactor to properly allocate resources for PF/VF") Cc: stable@dpdk.org Signed-off-by: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-10-09 11:11:21 +00:00
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
/* Forward */
rc = bnxt_hwrm_exec_fwd_resp(bp, fw_vf_id, fwd_cmd, req_len);
if (rc) {
net/bnxt: use dynamic log type This patch implements driver specific log type doing away with usage of RTE_LOG() for logging. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2018-01-26 17:31:55 +00:00
PMD_DRV_LOG(ERR,
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
"Failed to send FWD req VF 0x%x, type 0x%x.\n",
net/bnxt: fix allocation of PF info struct Fixes: 804e746c7b73 ("net/bnxt: add hardware resource manager init code") Cc: stable@dpdk.org Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2020-05-15 11:10:41 +00:00
fw_vf_id - bp->pf->first_vf_id,
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
rte_le_to_cpu_16(fwd_cmd->req_type));
}
return;
}
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
reject:
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
rc = bnxt_hwrm_reject_fwd_resp(bp, fw_vf_id, fwd_cmd, req_len);
if (rc) {
net/bnxt: use dynamic log type This patch implements driver specific log type doing away with usage of RTE_LOG() for logging. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2018-01-26 17:31:55 +00:00
PMD_DRV_LOG(ERR,
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
"Failed to send REJECT req VF 0x%x, type 0x%x.\n",
net/bnxt: fix allocation of PF info struct Fixes: 804e746c7b73 ("net/bnxt: add hardware resource manager init code") Cc: stable@dpdk.org Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2020-05-15 11:10:41 +00:00
fw_vf_id - bp->pf->first_vf_id,
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
rte_le_to_cpu_16(fwd_cmd->req_type));
}
return;
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
}
net/bnxt: use first completion ring for fwd and async event In order to save completion resource, use the first completion ring from PF or VF as the default completion ring for async event & HWRM forward response handling. Add bnxt_hwrm_set_async_event_cr() to set async_event_cr for either PF or VF. Fixes: 7bc8e9a227cc ("net/bnxt: support async link notification") Signed-off-by: Qingmin Liu <qingmin.liu@broadcom.com> Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2018-05-22 18:13:44 +00:00
int bnxt_event_hwrm_resp_handler(struct bnxt *bp, struct cmpl_base *cmp)
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
{
net/bnxt: use first completion ring for fwd and async event In order to save completion resource, use the first completion ring from PF or VF as the default completion ring for async event & HWRM forward response handling. Add bnxt_hwrm_set_async_event_cr() to set async_event_cr for either PF or VF. Fixes: 7bc8e9a227cc ("net/bnxt: support async link notification") Signed-off-by: Qingmin Liu <qingmin.liu@broadcom.com> Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2018-05-22 18:13:44 +00:00
bool evt = 0;
net/bnxt: handle VF/PF initialization appropriately 1) For a VF, query the firmware to determine if a MAC address is already configured. If not configure a random default MAC address. 2) Do not initialize the default completion ring in bnxt_alloc_hwrm_rings(). 3) While registering for async events with the firmware, use func_vf_cfg for a VF and use func_cfg for a PF. 4) Query the VNIC plcmode config using the bnxt_hwrm_vnic_plcmodes_qcfg before a VNIC is updated. Reconfigure the VNIC with the plcmode configuration queried earlier. Not doing this could overwrite the plcmodes in some cases. 5) Reorg the bnxt_handle_fwd_req to properly handle the forwarded requests. The previous code did not handle it completely. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-06-01 17:07:00 +00:00
net/bnxt: use first completion ring for fwd and async event In order to save completion resource, use the first completion ring from PF or VF as the default completion ring for async event & HWRM forward response handling. Add bnxt_hwrm_set_async_event_cr() to set async_event_cr for either PF or VF. Fixes: 7bc8e9a227cc ("net/bnxt: support async link notification") Signed-off-by: Qingmin Liu <qingmin.liu@broadcom.com> Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2018-05-22 18:13:44 +00:00
if (bp == NULL || cmp == NULL) {
PMD_DRV_LOG(ERR, "invalid NULL argument\n");
return evt;
}
net/bnxt: support hotplug This patch adds support for port hotplug framework. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2016-09-26 16:18:52 +00:00
net/bnxt: prevent device access when device is in reset Refactor init and uninit functions so that the driver can fail the eth_dev_ops callbacks and accessing Tx and Rx queues when device is in reset or in error state. Transmit and receive queues are freed during reset cleanup and reallocated during recovery. So we block all data path handling in this state. The eth_dev dev_started field is updated depending on the status of the device. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Reviewed-by: Santoshkumar Karanappa Rastapur <santosh.rastapur@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2019-10-02 01:23:22 +00:00
if (unlikely(is_bnxt_in_error(bp)))
return 0;
net/bnxt: use first completion ring for fwd and async event In order to save completion resource, use the first completion ring from PF or VF as the default completion ring for async event & HWRM forward response handling. Add bnxt_hwrm_set_async_event_cr() to set async_event_cr for either PF or VF. Fixes: 7bc8e9a227cc ("net/bnxt: support async link notification") Signed-off-by: Qingmin Liu <qingmin.liu@broadcom.com> Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2018-05-22 18:13:44 +00:00
switch (CMP_TYPE(cmp)) {
case CMPL_BASE_TYPE_HWRM_ASYNC_EVENT:
/* Handle any async event */
bnxt_handle_async_event(bp, cmp);
evt = 1;
break;
net/bnxt: fix PF support in SR-IOV mode 1. Implement HWRM_FUNC_VF_RESOURCE_CFG command and use it to reserve resources for VFs when NEW RM is enabled. 2. Invoke PF’s FUNC_CFG before configuring VFs resources. 3. Don’t consider max_rx_em_flows in max_l2_ctx calculation when VFs are configured. 4. Issue HWRM_FUNC_QCFG instead of HWRM_FUNC_QCAPS to find out the actual allocated resources for VF. 5. Don’t add random mac to the VF. 6. Handle completion type CMPL_BASE_TYPE_HWRM_FWD_REQ instead of CMPL_BASE_TYPE_HWRM_FWD_RESP. 7. Don't enable HWRM_FUNC_DRV_RGTR_INPUT_FLAGS_FWD_NONE_MODE when the list of HWRM commands that needs to be forwarded to the PF is specified in HWRM_FUNC_DRV_RGTR. 8. Update the HWRM commands list that can be forwarded to the PF. Fixes: b7778e8a1c00 ("net/bnxt: refactor to properly allocate resources for PF/VF") Cc: stable@dpdk.org Signed-off-by: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2020-10-09 11:11:21 +00:00
case CMPL_BASE_TYPE_HWRM_FWD_REQ:
net/bnxt: use first completion ring for fwd and async event In order to save completion resource, use the first completion ring from PF or VF as the default completion ring for async event & HWRM forward response handling. Add bnxt_hwrm_set_async_event_cr() to set async_event_cr for either PF or VF. Fixes: 7bc8e9a227cc ("net/bnxt: support async link notification") Signed-off-by: Qingmin Liu <qingmin.liu@broadcom.com> Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2018-05-22 18:13:44 +00:00
/* Handle HWRM forwarded responses */
bnxt_handle_fwd_req(bp, cmp);
evt = 1;
break;
default:
/* Ignore any other events */
net/bnxt: reduce verbosity of logs When IOMMU is available, EAL picks IOVA as VA as the default IOVA mode. This causes the bnxt driver to log warning messages saying "Memzone physical address same as virtual." and "Using rte_mem_virt2iova()" during load. Reduce the verbosity of logs to DEBUG. Reduced couple of other logs level to DEBUG as well. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Reviewed-by: Lance Richardson <lance.richardson@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2019-10-02 01:23:32 +00:00
PMD_DRV_LOG(DEBUG, "Ignoring %02x completion\n", CMP_TYPE(cmp));
net/bnxt: use first completion ring for fwd and async event In order to save completion resource, use the first completion ring from PF or VF as the default completion ring for async event & HWRM forward response handling. Add bnxt_hwrm_set_async_event_cr() to set async_event_cr for either PF or VF. Fixes: 7bc8e9a227cc ("net/bnxt: support async link notification") Signed-off-by: Qingmin Liu <qingmin.liu@broadcom.com> Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2018-05-22 18:13:44 +00:00
break;
}
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
net/bnxt: use first completion ring for fwd and async event In order to save completion resource, use the first completion ring from PF or VF as the default completion ring for async event & HWRM forward response handling. Add bnxt_hwrm_set_async_event_cr() to set async_event_cr for either PF or VF. Fixes: 7bc8e9a227cc ("net/bnxt: support async link notification") Signed-off-by: Qingmin Liu <qingmin.liu@broadcom.com> Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2018-05-22 18:13:44 +00:00
return evt;
net/bnxt: add completion ring Structures, macros, and functions for working with completion rings in the driver. Completion Ring is used by the Ethernet controller to provide the status of transmitted & received packets, report errors, report status changes to the host software, and inter-function forwarding requests. In addition to the generic ring features, a completion ring can have a statistics context that has statistics periodically DMAed to host memory, along with a consumer index. bnxt_handle_async_event() handles completions not related to a specific transmit or receive ring such as link status changes which arrive on the default completion ring. Other physical or virtual functions on the same device may send an HWRM command forward request. In this case, we will pass it through unvalidated. In the future, we will be able to have the PF monitor and control VF access to the HWRM interface if needed. New HWRM Calls: bnxt_hwrm_exec_fwd_resp: Execute an encapsulated command and forward the response. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com>
2016-06-15 21:23:08 +00:00
}
net/bnxt: handle error recovery FW event 1. Advertise HWRM_FUNC_DRV_RGTR_INPUT_FLAGS_ERROR_RECOVERY_SUPPORT flag in the FUNC_DRV_RGTR command. 2. request for the async event ASYNC_EVENT_CMPL_EVENT_ID_ERROR_RECOVERY in the FUNC_DRV_RGTR command. 3. handle the async event EVENT_ID_ERROR_RECOVERY from FW. Error recovery support will be used by firmware only if all the driver instances support error recovery process. Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
2019-10-02 01:23:28 +00:00
bool bnxt_is_master_func(struct bnxt *bp)
{
if (bp->recovery_info->flags & BNXT_FLAG_MASTER_FUNC)
return true;
return false;
}
bool bnxt_is_recovery_enabled(struct bnxt *bp)
{
struct bnxt_error_recovery_info *info;
info = bp->recovery_info;
if (info && (info->flags & BNXT_FLAG_RECOVERY_ENABLED))
return true;
return false;
}
net/bnxt: fix Rx performance by removing spinlock The spinlock was trying to protect scenarios where rx_queue stop/start could be initiated dynamically. Assigning bnxt_dummy_recv_pkts and bnxt_dummy_xmit_pkts immediately to avoid concurrent access of mbuf in Rx and cleanup path should help achieve the same result. Fixes: 14255b351537 ("net/bnxt: fix queue start/stop operations") Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com> Signed-off-by: Rahul Gupta <rahul.gupta@broadcom.com>
2020-10-26 03:56:16 +00:00
void bnxt_stop_rxtx(struct bnxt *bp)
{
bp->eth_dev->rx_pkt_burst = &bnxt_dummy_recv_pkts;
bp->eth_dev->tx_pkt_burst = &bnxt_dummy_xmit_pkts;
}
Reference in New Issue Copy Permalink