Hi Dave, all, Following your recommendation, I have submitted the standalone checker as an independent change:
https://gerrit.fd.io/r/c/vpp/+/46747 It checks one or more external plugin binaries and reports required libvnet function, object, and TLS symbols missing from the dynamic export set. It does not require the plugin sources or integration into the VPP build, and its use is documented. I validated it on ARM64 on top of the hidden-visibility series. It passed for 113 VPP consumers, including plugins, drivers, and crypto engines. An external adj_unlock consumer also passed, while synthetic missing function, object, and TLS exports were correctly reported. The remaining question is therefore the activation schedule for hidden visibility. This should be decided by the community during tomorrow's call. If the community chooses a transitional opt-in period, it should have an explicit end date or exit criterion; otherwise the non-default configuration risks receiving insufficient CI coverage. I suggest that the call conclude on: 1. whether the checker provides an adequate migration mechanism for out-of-tree plugins; 2. whether a transition period is needed and, if so, when it ends; 3. the merge and activation schedule for the series. I will report the discussion and outcome on this thread and ask participants to state their positions here as well. Best regards, Jerome
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#27172): https://lists.fd.io/g/vpp-dev/message/27172 Mute This Topic: https://lists.fd.io/mt/121139638/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
