Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH S32 07/15] ice: Check if VF is disabled for Opcode and other operations
Date: Fri, 1 Nov 2019 16:43:16 +0000	[thread overview]
Message-ID: <827d3dd5b3dd4e16ac6762f6070c1d95@intel.com> (raw)
In-Reply-To: <20191025143441.50151-7-anthony.l.nguyen@intel.com>

> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On
> Behalf Of Tony Nguyen
> Sent: Friday, October 25, 2019 7:35 AM
> To: intel-wired-lan at lists.osuosl.org
> Subject: [Intel-wired-lan] [PATCH S32 07/15] ice: Check if VF is disabled for
> Opcode and other operations
> 
> From: Akeem G Abodunrin <akeem.g.abodunrin@intel.com>
> 
> This patch adds code to check if PF or VF is disabled before honoring mailbox
> message to configure VF - If it is disabled, and opcode is for resetting VF, the
> PF driver simply tell VF that all is set. In addition, if reset is ongoing, and
> Admin intend to configure VF on the host, we can poll the VF enabling bit to
> make sure it is ready before continue - If after ~250 milliseconds, VF is not in
> active state, we can bail out with invalid error.
> 
> Signed-off-by: Akeem G Abodunrin <akeem.g.abodunrin@intel.com>
> ---
>  .../net/ethernet/intel/ice/ice_virtchnl_pf.c  | 74 ++++++++++++++++---
> .../net/ethernet/intel/ice/ice_virtchnl_pf.h  |  1 +
>  2 files changed, 63 insertions(+), 12 deletions(-)

Tested-by: Andrew Bowers <andrewx.bowers@intel.com>



  reply	other threads:[~2019-11-01 16:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 14:34 [Intel-wired-lan] [PATCH S32 01/15] ice: Use ice_ena_vsi and ice_dis_vsi in DCB configuration flow Tony Nguyen
2019-10-25 14:34 ` [Intel-wired-lan] [PATCH S32 02/15] ice: Add NDO callback to set the maximum per-queue bitrate Tony Nguyen
2019-11-01 16:41   ` Bowers, AndrewX
2019-10-25 14:34 ` [Intel-wired-lan] [PATCH S32 03/15] ice: Implement DCBNL support Tony Nguyen
2019-11-01 16:41   ` Bowers, AndrewX
2019-10-25 14:34 ` [Intel-wired-lan] [PATCH S32 04/15] ice: avoid setting features during reset Tony Nguyen
2019-11-01 16:42   ` Bowers, AndrewX
2019-10-25 14:34 ` [Intel-wired-lan] [PATCH S32 05/15] ice: Fix to change Rx/Tx ring descriptor size via ethtool with DCBx Tony Nguyen
2019-11-01 16:42   ` Bowers, AndrewX
2019-10-25 14:34 ` [Intel-wired-lan] [PATCH S32 06/15] ice: configure software LLDP in ice_init_pf_dcb Tony Nguyen
2019-11-01 16:42   ` Bowers, AndrewX
2019-10-25 14:34 ` [Intel-wired-lan] [PATCH S32 07/15] ice: Check if VF is disabled for Opcode and other operations Tony Nguyen
2019-11-01 16:43   ` Bowers, AndrewX [this message]
2019-10-25 14:34 ` [Intel-wired-lan] [PATCH S32 08/15] ice: Change max MSI-x vector_id check in cfg_irq_map Tony Nguyen
2019-11-01 16:43   ` Bowers, AndrewX
2019-10-25 14:34 ` [Intel-wired-lan] [PATCH S32 09/15] ice: use pkg_dwnld_status instead of sq_last_status Tony Nguyen
2019-11-01 16:43   ` Bowers, AndrewX
2019-10-25 14:34 ` [Intel-wired-lan] [PATCH S32 10/15] ice: delay less Tony Nguyen
2019-11-01 16:44   ` Bowers, AndrewX
2019-10-25 14:34 ` [Intel-wired-lan] [PATCH S32 11/15] ice: Update enum ice_flg64_bits to current specification Tony Nguyen
2019-11-01 16:44   ` Bowers, AndrewX
2019-10-25 14:34 ` [Intel-wired-lan] [PATCH S32 12/15] ice: remove unnecessary conditional check Tony Nguyen
2019-11-01 16:44   ` Bowers, AndrewX
2019-10-25 14:34 ` [Intel-wired-lan] [PATCH S32 13/15] ice: Introduce and use ice_vsi_type_str Tony Nguyen
2019-11-01 16:45   ` Bowers, AndrewX
2019-10-25 14:34 ` [Intel-wired-lan] [PATCH S32 14/15] ice: use more accurate ICE_DBG mask types Tony Nguyen
2019-11-01 16:45   ` Bowers, AndrewX
2019-10-25 14:34 ` [Intel-wired-lan] [PATCH S32 15/15] ice: print opcode when printing controlq errors Tony Nguyen
2019-11-01 16:45   ` Bowers, AndrewX
2019-11-01 16:41 ` [Intel-wired-lan] [PATCH S32 01/15] ice: Use ice_ena_vsi and ice_dis_vsi in DCB configuration flow Bowers, AndrewX

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=827d3dd5b3dd4e16ac6762f6070c1d95@intel.com \
    --to=andrewx.bowers@intel.com \
    --cc=intel-wired-lan@osuosl.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