From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
Cc: dpdk-dev <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: fix to prevent device access in error state
Date: Mon, 3 May 2021 21:01:51 -0700 [thread overview]
Message-ID: <CACZ4nhtg1e-Y=TmTbsWkr5m=_6tsfMmm6cjDtrN1CMMcPQ-LHA@mail.gmail.com> (raw)
In-Reply-To: <20210503052150.29189-1-kalesh-anakkur.purayil@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
On Sun, May 2, 2021 at 10:00 PM Kalesh A P <
kalesh-anakkur.purayil@broadcom.com> wrote:
> From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
>
> Driver should prevent any DMA with the device when it
> detects an error. When firmware is in fatal state,
> stop tx/rx by assigning them to dummy functions.
>
> Fixes: be14720def9c ("net/bnxt: support FW reset")
> Fixes: 9d0cbaecc91a ("net/bnxt: support periodic FW health monitoring")
> Cc: stable@dpdk.org
>
> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
> Reviewed-by: Andy Gospodarek <gospo@broadcom.com>
>
Patch applied to dpdk-next-net-brcm. Thanks
> ---
> drivers/net/bnxt/bnxt_ethdev.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/net/bnxt/bnxt_ethdev.c
> b/drivers/net/bnxt/bnxt_ethdev.c
> index 719eb68..822853a 100644
> --- a/drivers/net/bnxt/bnxt_ethdev.c
> +++ b/drivers/net/bnxt/bnxt_ethdev.c
> @@ -4275,6 +4275,8 @@ static void bnxt_check_fw_health(void *arg)
> bp->flags |= BNXT_FLAG_FATAL_ERROR;
> bp->flags |= BNXT_FLAG_FW_RESET;
>
> + bnxt_stop_rxtx(bp);
> +
> PMD_DRV_LOG(ERR, "Detected FW dead condition\n");
>
> if (bnxt_is_master_func(bp))
> --
> 2.10.1
>
>
prev parent reply other threads:[~2021-05-04 4:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 5:21 Kalesh A P
2021-05-04 4:01 ` Ajit Khaparde [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACZ4nhtg1e-Y=TmTbsWkr5m=_6tsfMmm6cjDtrN1CMMcPQ-LHA@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).