From: Bruce Richardson <bruce.richardson@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: Sandeep Penigalapati <sandeep.penigalapati@intel.com>,
<dev@dpdk.org>, Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
Jedrzej Jagielski <jedrzej.jagielski@intel.com>,
Andrzej Wilczynski <andrzejx.wilczynski@intel.com>,
<stable@dpdk.org>
Subject: Re: [PATCH] net/ixgbe: fix VF link status for E610
Date: Tue, 6 Oct 2026 12:00:34 +0100 [thread overview]
Message-ID: <asTU0sq4pqKkUthg@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <521f9c58-5da6-46c8-8064-2abf76585946@intel.com>
On Tue, Oct 06, 2026 at 12:38:48PM +0200, Burakov, Anatoly wrote:
> On 9/27/2026 7:52 PM, Sandeep Penigalapati wrote:
> > E610 VFs report a wrong link speed (e.g. 10G while the PF is at 1G)
> > because the speed is decoded from the VFLINKS register, which E610 does
> > not use for VF link state.
> >
> > Commit adbd71030575 ("net/ixgbe/base: fix link status for E610") added a
> > mailbox operation to fetch the link state from the PF and bumped the VF
> > mailbox API to 1.6, but the PMD never used it: ixgbevf_negotiate_api()
> > caps the API at 1.3 and ixgbevf_check_link() reads VFLINKS instead of the
> > base helper.
> >
> > Negotiate the mailbox API up to 1.6 and query the PF for the link state
> > on E610 VFs. Other MAC types are unchanged.
> >
> > Fixes: adbd71030575 ("net/ixgbe/base: fix link status for E610")
> > Cc: stable@dpdk.org
> > Signed-off-by: Sandeep Penigalapati <sandeep.penigalapati@intel.com>
> > ---
>
> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
>
Applied to dpdk-next-net-intel.
thanks,
/Bruce
prev parent reply other threads:[~2026-10-06 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 17:52 [PATCH] net/ixgbe: fix VF link status for E610 Sandeep Penigalapati
2026-10-06 10:38 ` Burakov, Anatoly
2026-10-06 11:00 ` Bruce Richardson [this message]
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=asTU0sq4pqKkUthg@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=andrzejx.wilczynski@intel.com \
--cc=dev@dpdk.org \
--cc=jedrzej.jagielski@intel.com \
--cc=sandeep.penigalapati@intel.com \
--cc=stable@dpdk.org \
--cc=vladimir.medvedkin@intel.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