From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: Mitch Williams <mitch.a.williams@intel.com>,
netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: [net-next 09/14] i40e: notify VF of all types of resets
Date: Thu, 5 Jun 2014 00:49:22 -0700 [thread overview]
Message-ID: <1401954567-13557-10-git-send-email-jeffrey.t.kirsher@intel.com> (raw)
In-Reply-To: <1401954567-13557-1-git-send-email-jeffrey.t.kirsher@intel.com>
From: Mitch Williams <mitch.a.williams@intel.com>
Currently, the PF driver only notifies the VFs for PF reset events.
Instead, notify the VFs for all types of resets, so they can attempt a
graceful reinit.
Change-ID: I03eb7afde25727198ef620f8b4e78bb667a11370
Signed-off-by: Mitch Williams <mitch.a.williams@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
---
drivers/net/ethernet/intel/i40e/i40e_main.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/net/ethernet/intel/i40e/i40e_main.c b/drivers/net/ethernet/intel/i40e/i40e_main.c
index b5a8a61..78666b3 100644
--- a/drivers/net/ethernet/intel/i40e/i40e_main.c
+++ b/drivers/net/ethernet/intel/i40e/i40e_main.c
@@ -4412,6 +4412,9 @@ void i40e_do_reset(struct i40e_pf *pf, u32 reset_flags)
WARN_ON(in_interrupt());
+ if (i40e_check_asq_alive(&pf->hw))
+ i40e_vc_notify_reset(pf);
+
/* do the biggest reset indicated */
if (reset_flags & (1 << __I40E_GLOBAL_RESET_REQUESTED)) {
@@ -5328,9 +5331,6 @@ static int i40e_prep_for_reset(struct i40e_pf *pf)
dev_dbg(&pf->pdev->dev, "Tearing down internal switch for reset\n");
- if (i40e_check_asq_alive(hw))
- i40e_vc_notify_reset(pf);
-
/* quiesce the VSIs and their queues that are not already DOWN */
i40e_pf_quiesce_all_vsi(pf);
--
1.9.3
next prev parent reply other threads:[~2014-06-05 7:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 7:49 [net-next 00/14][pull request] Intel Wired LAN Driver Updates 2014-06-05 Jeff Kirsher
2014-06-05 7:49 ` [net-next 01/14] i40e: don't use OR to check a value Jeff Kirsher
2014-06-05 7:49 ` [net-next 02/14] i40e: Allow disabling of DCB via debugfs Jeff Kirsher
2014-06-05 7:56 ` David Miller
2014-06-05 8:05 ` Jeff Kirsher
2014-06-05 7:49 ` [net-next 03/14] i40e: Rework register diagnostic Jeff Kirsher
2014-06-05 7:49 ` [net-next 04/14] i40e: remove check for large buffer Jeff Kirsher
2014-06-05 7:49 ` [net-next 05/14] i40e/i40evf: remove unused RX_LRO define Jeff Kirsher
2014-06-05 7:49 ` [net-next 06/14] i40e: clamp jumbo frame size Jeff Kirsher
2014-06-05 8:17 ` David Laight
2014-06-05 7:49 ` [net-next 07/14] i40evf: set descriptor multiple to 32 Jeff Kirsher
2014-06-05 7:49 ` [net-next 08/14] i40evf: fix crash when changing ring sizes Jeff Kirsher
2014-06-05 7:49 ` Jeff Kirsher [this message]
2014-06-05 7:49 ` [net-next 10/14] i40e/i40evf: VEB structure added, GTIME macro update Jeff Kirsher
2014-06-05 7:49 ` [net-next 11/14] i40e: refactor send version Jeff Kirsher
2014-06-05 7:49 ` [net-next 12/14] i40e: refactor stats collection Jeff Kirsher
2014-06-05 7:49 ` [net-next 13/14] i40e/i40evf: remove rx_errors and rx_missed Jeff Kirsher
2014-06-05 7:49 ` [net-next 14/14] i40e: add missing VSI statistics Jeff Kirsher
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=1401954567-13557-10-git-send-email-jeffrey.t.kirsher@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=mitch.a.williams@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.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).