From: Long Li <longli@microsoft.com>
To: dev@dpdk.org, Wei Hu <weh@microsoft.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: Long Li <longli@microsoft.com>
Subject: [PATCH v3 7/7] net/netvsc: handle VF recovery events for service reset
Date: Fri, 15 May 2026 12:28:41 -0700 [thread overview]
Message-ID: <20260515192843.552762-8-longli@microsoft.com> (raw)
In-Reply-To: <20260515192843.552762-1-longli@microsoft.com>
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: defer data path switch to synthetic via
rte_eal_alarm_set, keeping VF attached in DPDK
- On RECOVERY_SUCCESS: defer data path switch back to VF
- On RECOVERY_FAILED: do full VF removal (same as INTR_RMV)
- Unregister all recovery callbacks and cancel pending alarms
during detach, removal, and close
All recovery callbacks defer work via rte_eal_alarm_set, consistent
with the existing INTR_RMV pattern, to avoid cross-driver lock-order
assumptions in event-callback context.
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.
This change is compatible with the current behavior when no
service reset messages are received.
Signed-off-by: Long Li <longli@microsoft.com>
---
v3:
- Deferred recovering and recovery_success callbacks via
rte_eal_alarm_set, consistent with INTR_RMV pattern
- Dropped unlocked vf_attached guard in recovery_failed
- Cancel new deferred alarms in hn_vf_close
v2:
- Added dev_started check in recovery_success
- Added vf_attached guard in recovery_failed
- Added comment explaining direct lock acquisition
drivers/net/netvsc/hn_vf.c | 165 +++++++++++++++++++++++++++++++++++++
1 file changed, 165 insertions(+)
diff --git a/drivers/net/netvsc/hn_vf.c b/drivers/net/netvsc/hn_vf.c
index c83cc973fd..27c46ce404 100644
--- a/drivers/net/netvsc/hn_vf.c
+++ b/drivers/net/netvsc/hn_vf.c
@@ -50,6 +50,13 @@ static int hn_vf_match(const struct rte_eth_dev *dev)
}
+static int hn_eth_recovering_callback(uint16_t port_id,
+ enum rte_eth_event_type event, void *cb_arg, void *out);
+static int hn_eth_recovery_success_callback(uint16_t port_id,
+ enum rte_eth_event_type event, void *cb_arg, void *out);
+static int hn_eth_recovery_failed_callback(uint16_t port_id,
+ enum rte_eth_event_type event, void *cb_arg, void *out);
+
/*
* Attach new PCI VF device and return the port_id
*/
@@ -111,7 +118,56 @@ static int hn_vf_attach(struct rte_eth_dev *dev, struct hn_data *hv)
return ret;
}
+ /* Register recovery event callbacks for service reset handling */
+ ret = rte_eth_dev_callback_register(hv->vf_ctx.vf_port,
+ RTE_ETH_EVENT_ERR_RECOVERING,
+ hn_eth_recovering_callback, hv);
+ if (ret) {
+ PMD_DRV_LOG(ERR,
+ "Registering recovering callback failed for vf port %d ret %d",
+ port, ret);
+ goto err_recovering;
+ }
+
+ ret = rte_eth_dev_callback_register(hv->vf_ctx.vf_port,
+ RTE_ETH_EVENT_RECOVERY_SUCCESS,
+ hn_eth_recovery_success_callback, hv);
+ if (ret) {
+ PMD_DRV_LOG(ERR,
+ "Registering recovery success callback failed for vf port %d ret %d",
+ port, ret);
+ goto err_recovery_success;
+ }
+
+ ret = rte_eth_dev_callback_register(hv->vf_ctx.vf_port,
+ RTE_ETH_EVENT_RECOVERY_FAILED,
+ hn_eth_recovery_failed_callback, hv);
+ if (ret) {
+ PMD_DRV_LOG(ERR,
+ "Registering recovery failed callback failed for vf port %d ret %d",
+ port, ret);
+ goto err_recovery_failed;
+ }
+
return 0;
+
+err_recovery_failed:
+ rte_eth_dev_callback_unregister(hv->vf_ctx.vf_port,
+ RTE_ETH_EVENT_RECOVERY_SUCCESS,
+ hn_eth_recovery_success_callback, hv);
+err_recovery_success:
+ rte_eth_dev_callback_unregister(hv->vf_ctx.vf_port,
+ RTE_ETH_EVENT_ERR_RECOVERING,
+ hn_eth_recovering_callback, hv);
+err_recovering:
+ rte_eth_dev_callback_unregister(hv->vf_ctx.vf_port,
+ RTE_ETH_EVENT_INTR_RMV,
+ hn_eth_rmv_event_callback, hv);
+ hv->vf_ctx.vf_attached = false;
+ hv->vf_ctx.vf_port = 0;
+ if (rte_eth_dev_owner_unset(port, hv->owner.id) < 0)
+ PMD_DRV_LOG(ERR, "Failed to unset owner for port %d", port);
+ return ret;
}
static void hn_vf_remove_unlocked(struct hn_data *hv);
@@ -143,6 +199,12 @@ static void hn_remove_delayed(void *args)
PMD_DRV_LOG(ERR,
"rte_eth_dev_callback_unregister failed ret=%d",
ret);
+ rte_eth_dev_callback_unregister(port_id, RTE_ETH_EVENT_ERR_RECOVERING,
+ hn_eth_recovering_callback, hv);
+ rte_eth_dev_callback_unregister(port_id, RTE_ETH_EVENT_RECOVERY_SUCCESS,
+ hn_eth_recovery_success_callback, hv);
+ rte_eth_dev_callback_unregister(port_id, RTE_ETH_EVENT_RECOVERY_FAILED,
+ hn_eth_recovery_failed_callback, hv);
/* Detach and release port_id from system */
ret = rte_eth_dev_stop(port_id);
@@ -187,6 +249,89 @@ int hn_eth_rmv_event_callback(uint16_t port_id,
return 0;
}
+/*
+ * Deferred handler for VF error recovery event.
+ * Switch data path to synthetic but keep the VF attached.
+ */
+static void hn_recovering_delayed(void *args)
+{
+ struct hn_data *hv = args;
+
+ rte_rwlock_write_lock(&hv->vf_lock);
+ hn_vf_remove_unlocked(hv);
+ rte_rwlock_write_unlock(&hv->vf_lock);
+}
+
+static int
+hn_eth_recovering_callback(uint16_t port_id,
+ enum rte_eth_event_type event __rte_unused,
+ void *cb_arg, void *out __rte_unused)
+{
+ struct hn_data *hv = cb_arg;
+
+ PMD_DRV_LOG(NOTICE, "VF port %u recovering from error", port_id);
+ rte_eal_alarm_set(1, hn_recovering_delayed, hv);
+
+ return 0;
+}
+
+/*
+ * Deferred handler for VF recovery success event.
+ * Switch data path back to VF.
+ */
+static void hn_recovery_success_delayed(void *args)
+{
+ struct hn_data *hv = args;
+ struct rte_eth_dev *dev = &rte_eth_devices[hv->port_id];
+ int ret;
+
+ rte_rwlock_write_lock(&hv->vf_lock);
+ /* Only switch data path to VF if the netvsc device is started,
+ * mirroring the check in hn_vf_add_unlocked. If the device was
+ * stopped during recovery, defer to hn_vf_start().
+ */
+ if (dev->data->dev_started &&
+ hv->vf_ctx.vf_attached && !hv->vf_ctx.vf_vsc_switched) {
+ ret = hn_nvs_set_datapath(hv, NVS_DATAPATH_VF);
+ if (ret)
+ PMD_DRV_LOG(ERR,
+ "Failed to switch to VF after recovery");
+ else
+ hv->vf_ctx.vf_vsc_switched = true;
+ }
+ rte_rwlock_write_unlock(&hv->vf_lock);
+}
+
+static int
+hn_eth_recovery_success_callback(uint16_t port_id,
+ enum rte_eth_event_type event __rte_unused,
+ void *cb_arg, void *out __rte_unused)
+{
+ struct hn_data *hv = cb_arg;
+
+ PMD_DRV_LOG(NOTICE, "VF port %u recovery succeeded", port_id);
+ rte_eal_alarm_set(1, hn_recovery_success_delayed, hv);
+
+ return 0;
+}
+
+/*
+ * Handle VF recovery failure event from MANA PMD.
+ * VF is unusable, do full removal.
+ */
+static int
+hn_eth_recovery_failed_callback(uint16_t port_id,
+ enum rte_eth_event_type event __rte_unused,
+ void *cb_arg, void *out __rte_unused)
+{
+ struct hn_data *hv = cb_arg;
+
+ PMD_DRV_LOG(NOTICE, "VF port %u recovery failed, removing", port_id);
+ rte_eal_alarm_set(1, hn_remove_delayed, hv);
+
+ return 0;
+}
+
static int hn_setup_vf_queues(int port, struct rte_eth_dev *dev)
{
struct hn_rx_queue *rx_queue;
@@ -247,6 +392,12 @@ static void hn_vf_detach(struct hn_data *hv)
rte_eth_dev_callback_unregister(port, RTE_ETH_EVENT_INTR_RMV,
hn_eth_rmv_event_callback, hv);
+ rte_eth_dev_callback_unregister(port, RTE_ETH_EVENT_ERR_RECOVERING,
+ hn_eth_recovering_callback, hv);
+ rte_eth_dev_callback_unregister(port, RTE_ETH_EVENT_RECOVERY_SUCCESS,
+ hn_eth_recovery_success_callback, hv);
+ rte_eth_dev_callback_unregister(port, RTE_ETH_EVENT_RECOVERY_FAILED,
+ hn_eth_recovery_failed_callback, hv);
if (rte_eth_dev_owner_unset(port, hv->owner.id) < 0)
PMD_DRV_LOG(ERR, "Failed to unset owner for port %d", port);
@@ -630,7 +781,21 @@ int hn_vf_close(struct rte_eth_dev *dev)
RTE_ETH_EVENT_INTR_RMV,
hn_eth_rmv_event_callback,
hv);
+ rte_eth_dev_callback_unregister(hv->vf_ctx.vf_port,
+ RTE_ETH_EVENT_ERR_RECOVERING,
+ hn_eth_recovering_callback,
+ hv);
+ rte_eth_dev_callback_unregister(hv->vf_ctx.vf_port,
+ RTE_ETH_EVENT_RECOVERY_SUCCESS,
+ hn_eth_recovery_success_callback,
+ hv);
+ rte_eth_dev_callback_unregister(hv->vf_ctx.vf_port,
+ RTE_ETH_EVENT_RECOVERY_FAILED,
+ hn_eth_recovery_failed_callback,
+ hv);
rte_eal_alarm_cancel(hn_remove_delayed, hv);
+ rte_eal_alarm_cancel(hn_recovering_delayed, hv);
+ rte_eal_alarm_cancel(hn_recovery_success_delayed, hv);
ret = rte_eth_dev_close(hv->vf_ctx.vf_port);
hv->vf_ctx.vf_attached = false;
}
--
2.43.0
prev parent reply other threads:[~2026-05-15 19:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 2:05 [PATCH v2 1/7] net/netvsc: retry VF hotplug indefinitely until PCI device disappears Long Li
2026-05-06 2:05 ` [PATCH v2 2/7] net/netvsc: retry on SIOCGIFHWADDR failure during VF hotplug Long Li
2026-05-06 2:05 ` [PATCH v2 3/7] net/netvsc: retry full probe when IB device not ready during hotplug Long Li
2026-05-06 2:05 ` [PATCH v2 4/7] net/netvsc: add debug logging for VF hotplug retry Long Li
2026-05-06 2:05 ` [PATCH v2 5/7] net/netvsc: retry when no matching MAC found in net directory Long Li
2026-05-06 2:05 ` [PATCH v2 6/7] net/netvsc: forward per-queue stats from VF device Long Li
2026-05-06 2:05 ` [PATCH v2 7/7] net/netvsc: handle VF recovery events for service reset Long Li
2026-05-07 2:49 ` [PATCH v2 1/7] net/netvsc: retry VF hotplug indefinitely until PCI device disappears Stephen Hemminger
2026-05-15 19:45 ` [EXTERNAL] " Long Li
2026-05-15 19:28 ` [PATCH v3 0/7] net/netvsc: fix VF hotplug and service reset handling Long Li
2026-05-15 19:28 ` [PATCH v3 1/7] net/netvsc: retry VF hotplug indefinitely until PCI device disappears Long Li
2026-05-15 19:28 ` [PATCH v3 2/7] net/netvsc: retry on SIOCGIFHWADDR failure during VF hotplug Long Li
2026-05-15 19:28 ` [PATCH v3 3/7] net/netvsc: retry full probe when IB device not ready during hotplug Long Li
2026-05-15 19:28 ` [PATCH v3 4/7] net/netvsc: add debug logging for VF hotplug retry Long Li
2026-05-15 19:28 ` [PATCH v3 5/7] net/netvsc: retry when no matching MAC found in net directory Long Li
2026-05-15 19:28 ` [PATCH v3 6/7] net/netvsc: forward per-queue stats from VF device Long Li
2026-05-15 19:28 ` Long Li [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=20260515192843.552762-8-longli@microsoft.com \
--to=longli@microsoft.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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