From: Breno Leitao <leitao@debian.org>
To: Satish Kharat <satishkh@cisco.com>
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 v7 01/10] enic: verify firmware supports V2 SR-IOV at probe time
Date: Thu, 14 May 2026 02:13:42 -0700 [thread overview]
Message-ID: <agWHnleaodwTcBKr@gmail.com> (raw)
In-Reply-To: <20260513-enic-sriov-v2-admin-channel-v2-v7-1-68b9f4141f4c@cisco.com>
On Wed, May 13, 2026 at 08:15:38AM -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.
>
> The VIC_FEATURE_SRIOV enum value (4) matches the firmware ABI. A
> placeholder entry (VIC_FEATURE_PTP at position 3) is added to keep
> the enum in sync with firmware's feature numbering.
Should you do something like the following, then?
enum vic_feature_t {
VIC_FEATURE_VXLAN,
VIC_FEATURE_RDMA,
VIC_FEATURE_VXLAN_PATCH,
/* slot 3 reserved for firmware VIC_FEATURE_PTP */
VIC_FEATURE_SRIOV = 4,
VIC_FEATURE_MAX,
};
> +
> + if (enic->vf_type != ENIC_VF_TYPE_V2)
> + return;
> +
> + /* A successful command means firmware recognizes
> + * VIC_FEATURE_SRIOV; supported_versions is available
> + * for sub-feature versioning in the future.
> + */
> + err = vnic_dev_get_supported_feature_ver(enic->vdev,
> + VIC_FEATURE_SRIOV,
> + &supported_versions,
> + &a1);
In this case supported_versions and a1 are written but never read, does the API
need some refactor ?
next prev parent reply other threads:[~2026-05-14 9:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 15:15 [PATCH net-next v7 00/10] enic: SR-IOV V2 admin channel and MBOX protocol Satish Kharat
2026-05-13 15:15 ` [PATCH net-next v7 01/10] enic: verify firmware supports V2 SR-IOV at probe time Satish Kharat
2026-05-14 9:13 ` Breno Leitao [this message]
2026-05-13 15:15 ` [PATCH net-next v7 02/10] enic: add admin channel open and close for SR-IOV Satish Kharat
2026-05-13 15:15 ` [PATCH net-next v7 03/10] enic: add admin RQ buffer management Satish Kharat
2026-05-13 15:15 ` [PATCH net-next v7 04/10] enic: add admin CQ service with MSI-X interrupt and NAPI polling Satish Kharat
2026-05-13 15:15 ` [PATCH net-next v7 05/10] enic: define MBOX message types and header structures Satish Kharat
2026-05-13 15:15 ` [PATCH net-next v7 06/10] enic: add MBOX core send and receive for admin channel Satish Kharat
2026-05-13 15:15 ` [PATCH net-next v7 07/10] enic: add MBOX PF handlers for VF register and capability Satish Kharat
2026-05-13 15:15 ` [PATCH net-next v7 08/10] enic: add MBOX VF handlers for capability, register and link state Satish Kharat
2026-05-13 15:15 ` [PATCH net-next v7 09/10] enic: wire V2 SR-IOV enable with admin channel and MBOX Satish Kharat
2026-05-13 15:15 ` [PATCH net-next v7 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=agWHnleaodwTcBKr@gmail.com \
--to=leitao@debian.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=satishkh@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.