From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dpdk-dev <dev@dpdk.org>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] net/bnxt: fix seg fault on Thor
Date: Fri, 30 Jul 2021 15:27:40 -0700 [thread overview]
Message-ID: <CACZ4nhuVc38uXBDiFdB3RRXt3Je+Xw4wBozHBF=i2sMju+kRhA@mail.gmail.com> (raw)
In-Reply-To: <20210730211545.16425-1-ajit.khaparde@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
On Fri, Jul 30, 2021 at 2:15 PM Ajit Khaparde
<ajit.khaparde@broadcom.com> wrote:
>
> In a few cases with Thor device, PMD can segfault when VF
> representors are specified. Temporarily fix it by preventing
> VF reps for Thor device. This will be addressed in next release.
>
> Fixes: 3fe124d2536c ("net/bnxt: support Thor platform")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
Updated the commit headline to
"net/bnxt: disable VF representors on Thor"
Merged to dpdk-next-net-brcm.
> ---
> drivers/net/bnxt/tf_ulp/bnxt_ulp.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/net/bnxt/tf_ulp/bnxt_ulp.c b/drivers/net/bnxt/tf_ulp/bnxt_ulp.c
> index fa2148ead7..dbf85e4eda 100644
> --- a/drivers/net/bnxt/tf_ulp/bnxt_ulp.c
> +++ b/drivers/net/bnxt/tf_ulp/bnxt_ulp.c
> @@ -815,6 +815,11 @@ ulp_ctx_init(struct bnxt *bp,
> goto error_deinit;
> }
>
> + if (devid == BNXT_ULP_DEVICE_ID_THOR) {
> + ulp_data->ulp_flags &= ~BNXT_ULP_VF_REP_ENABLED;
> + BNXT_TF_DBG(ERR, "Enabled non-VFR mode\n");
> + }
> +
> /*
> * Shared session must be created before first regular session but after
> * the ulp_ctx is valid.
> --
> 2.21.1 (Apple Git-122.3)
>
prev parent reply other threads:[~2021-07-30 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 21:15 Ajit Khaparde
2021-07-30 22:27 ` 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='CACZ4nhuVc38uXBDiFdB3RRXt3Je+Xw4wBozHBF=i2sMju+kRhA@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).