From: Rasesh Mody <rmody@marvell.com>
To: Manish Chopra <manishc@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
Jerin Jacob <jerinjacobk@gmail.com>
Cc: GR-Everest-DPDK-Dev <GR-Everest-DPDK-Dev@marvell.com>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 1/2] net/qede: Fix VF re-load failure after ungraceful termination of DPDK
Date: Fri, 7 Feb 2020 06:22:18 +0000 [thread overview]
Message-ID: <BYAPR18MB283800CE9B752804A9A9E3AFB51D0@BYAPR18MB2838.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20200206200146.14808-1-manishc@marvell.com>
+Jerin
>From: dev <dev-bounces@dpdk.org> On Behalf Of Manish Chopra
>Sent: Thursday, February 06, 2020 12:02 PM
>
>On ungraceful termination of DPDK application, PMD VF driver fails to re-load
>due to PF seeing the VF in unexpected state during VF acquisition handshake.
>
>This patch fixes it by allowing VF to request the PF for soft FLR during the load
>in such cases so that it can get cleanly re-loaded.
>
>Fixes: 2ea6f76aff40 ("qede: add core driver")
Cc: stable@dpdk.org
>
>Signed-off-by: Manish Chopra <manishc@marvell.com>
>Signed-off-by: Shahed Shaikh <shshaikh@marvell.com>
>Signed-off-by: Rasesh Mody <rmody@marvell.com>
>---
Acked-by: Rasesh Mody <rmody@marvell.com>
next prev parent reply other threads:[~2020-02-07 6:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200206200146.14808-1-manishc@marvell.com>
2020-02-06 20:01 ` [dpdk-stable] [PATCH 2/2] net/qede: Do not stop vport if not started Manish Chopra
2020-02-07 6:22 ` Rasesh Mody [this message]
2020-02-15 13:33 ` [dpdk-stable] [dpdk-dev] [PATCH 1/2] net/qede: Fix VF re-load failure after ungraceful termination of DPDK Jerin Jacob
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=BYAPR18MB283800CE9B752804A9A9E3AFB51D0@BYAPR18MB2838.namprd18.prod.outlook.com \
--to=rmody@marvell.com \
--cc=GR-Everest-DPDK-Dev@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinjacobk@gmail.com \
--cc=manishc@marvell.com \
--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).