From: Stephen Hemminger <stephen@networkplumber.org>
To: Wei Hu <weh@microsoft.com>
Cc: dev@dpdk.org, stable@dpdk.org, longli@microsoft.com
Subject: Re: [PATCH 2/2] net/netvsc: handle VF recovery events for service reset
Date: Wed, 29 Apr 2026 07:56:41 -0700 [thread overview]
Message-ID: <20260429075641.14de6610@phoenix.local> (raw)
In-Reply-To: <20260429084955.39164-3-weh@microsoft.com>
On Wed, 29 Apr 2026 01:49:55 -0700
Wei Hu <weh@microsoft.com> wrote:
> Register callbacks for RTE_ETH_EVENT_ERR_RECOVERING,
> RTE_ETH_EVENT_RECOVERY_SUCCESS, and RTE_ETH_EVENT_RECOVERY_FAILED
> events on the VF port to handle MANA service resets.
>
> - On ERR_RECOVERING: switch data path to synthetic but keep the
> VF device attached in DPDK
> - On RECOVERY_SUCCESS: switch data path back to VF
> - On RECOVERY_FAILED: do full VF removal (same as INTR_RMV)
> - Unregister all recovery callbacks during detach, removal, and
> close
>
> This ensures that during a service reset (kernel suspend/resume
> without PCI remove), netvsc keeps the VF attached and seamlessly
> switches back to it after recovery, without requiring a PCI
> hot-add event.
>
> Signed-off-by: Long Li <longli@microsoft.com>
> Signed-off-by: Wei Hu <weh@microsoft.com>
> ---
This patch is failing build.
Clang with lock annotations is seeing problems
prev parent reply other threads:[~2026-04-29 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 8:49 [PATCH 0/2] net/mana: add device reset support for service events Wei Hu
2026-04-29 8:49 ` [PATCH 1/2] net/mana: add device reset support Wei Hu
2026-04-29 8:49 ` [PATCH 2/2] net/netvsc: handle VF recovery events for service reset Wei Hu
2026-04-29 14:56 ` Stephen Hemminger [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=20260429075641.14de6610@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=longli@microsoft.com \
--cc=stable@dpdk.org \
--cc=weh@microsoft.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