[RFC,2/3] net/bnxt: notify applications about device reset
Checks
Commit Message
From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
When the driver receives RESET_NOTIFY async event from FW or detected
an error condition, it should update the application that FW is going
to reset. Once the driver recoveres from the reset, update the reset
recovery status to application as well.
The recovery process is transparent to the application as the driver
itself tries to recover from FW reset or FW error conditions.
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>
---
drivers/net/bnxt/bnxt_cpr.c | 3 +++
drivers/net/bnxt/bnxt_ethdev.c | 10 ++++++++++
2 files changed, 13 insertions(+)
@@ -76,6 +76,9 @@ void bnxt_handle_async_event(struct bnxt *bp,
PMD_DRV_LOG(INFO, "Port conn async event\n");
break;
case HWRM_ASYNC_EVENT_CMPL_EVENT_ID_RESET_NOTIFY:
+ _rte_eth_dev_callback_process(bp->eth_dev,
+ RTE_ETH_EVENT_INTR_RESET,
+ NULL);
event_data = rte_le_to_cpu_32(async_cmp->event_data1);
/* timestamp_lo/hi values are in units of 100ms */
bp->fw_reset_max_msecs = async_cmp->timestamp_hi ?
@@ -4021,11 +4021,17 @@ static void bnxt_dev_recover(void *arg)
goto err;
PMD_DRV_LOG(INFO, "Recovered from FW reset\n");
+ _rte_eth_dev_callback_process(bp->eth_dev,
+ RTE_ETH_EVENT_RECOVERED,
+ NULL);
return;
err:
bp->flags |= BNXT_FLAG_FATAL_ERROR;
bnxt_uninit_resources(bp, false);
PMD_DRV_LOG(ERR, "Failed to recover from FW reset\n");
+ _rte_eth_dev_callback_process(bp->eth_dev,
+ RTE_ETH_EVENT_INTR_RMV,
+ NULL);
}
void bnxt_dev_reset_and_resume(void *arg)
@@ -4160,6 +4166,10 @@ static void bnxt_check_fw_health(void *arg)
bp->flags |= BNXT_FLAG_FATAL_ERROR;
bp->flags |= BNXT_FLAG_FW_RESET;
+ _rte_eth_dev_callback_process(bp->eth_dev,
+ RTE_ETH_EVENT_INTR_RESET,
+ NULL);
+
PMD_DRV_LOG(ERR, "Detected FW dead condition\n");
if (bnxt_is_master_func(bp))