Netdev List
 help / color / mirror / Atom feed
From: Satish Kharat <satishkh@cisco.com>
To: Breno Leitao <leitao@debian.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sesidhar Baddela <sebaddel@cisco.com>
Subject: Re: [PATCH net-next v8 01/10] enic: verify firmware supports V2 SR-IOV at probe time
Date: Tue, 9 Jun 2026 11:24:39 -0700	[thread overview]
Message-ID: <99bbd283-84a0-47b8-9e2c-e3d412ad03cd@cisco.com> (raw)
In-Reply-To: <aihNYOiYUc3p1Y6_@gmail.com>

/"Can we get here with SR-IOV enabled? Then we want to disable it on 
failure."/

No — enic_sriov_detect_vf_type() runs during early probe, before any 
SR-IOV enablement path executes.
The auto-enable path (for pre-configured VFs at boot) runs later in 
enic_probe() and already skips V2:
if (enic->num_vfs && enic->vf_type != ENIC_VF_TYPE_V2) { err = 
pci_enable_sriov(pdev, enic->num_vfs);
The user-triggered path (sriov_configure) also checks vf_type and 
returns -EOPNOTSUPP when it is
ENIC_VF_TYPE_NONE.
So at the point where this function downgrades vf_type to 
ENIC_VF_TYPE_NONE, SR-IOV has not been enabled
  and there is nothing to disable

On 6/9/26 10:30, Breno Leitao wrote:
> On Tue, Jun 09, 2026 at 09:32:27AM -0700, Satish Kharat wrote:
>> During PF probe, query the firmware get-supported-feature interface
>> to verify that the running firmware supports V2 SR-IOV. Firmware
>> version 5.3(4.72) and later report VIC_FEATURE_SRIOV via
>> CMD_GET_SUPP_FEATURE_VER. If the firmware does not support the
>> feature, set vf_type to ENIC_VF_TYPE_NONE and log a warning so the
>> admin knows a firmware upgrade is needed.
>>
>> VIC_FEATURE_SRIOV is assigned the explicit value 4 to match the
>> firmware ABI.  Slot 3 (firmware's VIC_FEATURE_PTP) is reserved with
>> a comment rather than a placeholder enum entry, since PTP is not
>> used by the upstream driver.
>>
>> Suggested-by: Breno Leitao <leitao@debian.org>
>> Signed-off-by: Satish Kharat <satishkh@cisco.com>
>> ---
>>   drivers/net/ethernet/cisco/enic/enic_main.c   | 21 ++++++++++++++++++++-
>>   drivers/net/ethernet/cisco/enic/vnic_devcmd.h |  2 ++
>>   2 files changed, 22 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/ethernet/cisco/enic/enic_main.c b/drivers/net/ethernet/cisco/enic/enic_main.c
>> index e7125b818087..53d68272d06a 100644
>> --- a/drivers/net/ethernet/cisco/enic/enic_main.c
>> +++ b/drivers/net/ethernet/cisco/enic/enic_main.c
>> @@ -2641,8 +2641,10 @@ static void enic_iounmap(struct enic *enic)
>>   static void enic_sriov_detect_vf_type(struct enic *enic)
>>   {
>>   	struct pci_dev *pdev = enic->pdev;
>> -	int pos;
>> +	u64 supported_versions, a1 = 0;
>>   	u16 vf_dev_id;
>> +	int pos;
>> +	int err;
>>   
>>   	if (enic_is_sriov_vf(enic) || enic_is_dynamic(enic))
>>   		return;
>> @@ -2669,6 +2671,23 @@ static void enic_sriov_detect_vf_type(struct enic *enic)
>>   		enic->vf_type = ENIC_VF_TYPE_NONE;
>>   		break;
>>   	}
>> +
>> +	if (enic->vf_type != ENIC_VF_TYPE_V2)
> Can we get here with SR-IOV enabled? Then we want to disable it on
> failure.

  reply	other threads:[~2026-06-09 18:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09 16:32 [PATCH net-next v8 00/10] enic: SR-IOV V2 admin channel and MBOX protocol Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 01/10] enic: verify firmware supports V2 SR-IOV at probe time Satish Kharat
2026-06-09 17:30   ` Breno Leitao
2026-06-09 18:24     ` Satish Kharat [this message]
2026-06-09 16:32 ` [PATCH net-next v8 02/10] enic: add admin channel open and close for SR-IOV Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 03/10] enic: add admin RQ buffer management Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 04/10] enic: add admin CQ service with MSI-X interrupt and workqueue polling Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 05/10] enic: define MBOX message types and header structures Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 06/10] enic: add MBOX core send and receive for admin channel Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 07/10] enic: add MBOX PF handlers for VF register and capability Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 08/10] enic: add MBOX VF handlers for capability, register and link state Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 09/10] enic: wire V2 SR-IOV enable with admin channel and MBOX Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 10/10] enic: add V2 VF probe with admin channel and PF registration Satish Kharat

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=99bbd283-84a0-47b8-9e2c-e3d412ad03cd@cisco.com \
    --to=satishkh@cisco.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sebaddel@cisco.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