On Fri, Apr 03, 2026 at 05:08:36PM +0100, Bruce Richardson wrote: > On Tue, Mar 31, 2026 at 01:01:16PM +0000, Ciara Loftus wrote: > > Previously, VF recovery from PF-initiated resets required explicit > > opt-in via auto_reset, leaving VFs non-functional by default after a > > reset unless the application handled it. This series makes transparent > > recovery including the restoration of settings the default, and > > implements some fixes related to the reset path as well. > > > > Patch 1 fixes a regression which prevented promiscuous mode from being > > disabled before sending the RESET_VF message to the PF during device > > close. > > > > Patch 2 enables the auto_reset and no-poll-on-link-down devargs > > by default so VFs recover from resets without the need to introduce any > > reset handling in the application. > > > > Patch 3 introduces a new auto_reconfig devarg (on by default) which > > extends the recovery path to restore unicast and multicast promiscuous > > state after a reset. Restoration of additional settings such as VLAN > > filters could be added under the same mechanism in a follow-up series. > > > > Patch 4 fixes a minor logging issue. > > > > Ciara Loftus (4): > > net/iavf: fix disabling of promiscuous modes on device close > > net/iavf: enable auto reset by default > > net/iavf: enable post-reset restoration of VF settings > > net/iavf: fix reset handling error log > > > Series-Acked-by: Bruce Richardson <[email protected]> > Applied to dpdk-next-net-intel.
Thanks, /Bruce
