Another attempt to address the tracepoint ABI problem

We had a variant of that in Solaris, specifically in the libraries, which had to be both stable and changable (;-))

David J. Brown attached version numbers to function entry points, like SUNW_1.1 (for something public: SUNWprivate for everything else). If the entry point changed, even if the function signature was the same, the number got bumped to SUNW_1.2.

If a tracepoint points to a function to attach a BPF script to, the script for that tracepoint can check if the function version has changed, and if it has, the person using it can go and do a "git blame" hunt to see what they need to do.

--dave
see also https://www.usenix.org/legacy/publications/library/procee... and my note about it, https://leaflessca.wordpress.com/2017/02/12/dll-hell-and-...