/* $NetBSD: TODO.compat-module,v 1.1.2.12 2018/09/25 21:44:30 pgoyette Exp $ */ DONE ---- 1. Removed the building of the compat library - it is no longer needed. 2. Reverted some intentional auto-load breakage for loading the sysv_ipc module; the breakage was introduced as the fix for the above-mentioned build breakage. 3. Split the sysv_ipc compat routines into their own compat_sysv module. 4. Resolved some inter-module dependencies. 5. Extracted some net/if.c compat routines into the compat module, and replaced the originals with indirect (vectored) function calls. 6. Reconfirmed existing compat-module dependencies, and update the defopt/defflag lines in the config files* as needed, to insure that built-in dependencies get resolved. 7. Fixed limits on the number of module depedencies and maximum recursion level have been removed. Previous code for reporting module status to userland has been versioned and moved to the compat_80 module. 8. The old monolithic compat module has been broken into multiple modules, one for each old NetBSD version. The monolithic module is no longer available. Similarly, the compat_sysv module has also been split into several version-specific modules, and the mini-monolithic compat_sysv module is no longer provided. 9. syscalls.master has been updated to autoload the version-specific compat modules rather than the monolithic modules. 10. Separated COMPAT_BSDPTY stuff, allowing the COMPAT_60 module to be built regardless. 11. Implemented a MP-safe mechanism for installing and removing function pointers. Thanks to riastradh@ for the template code. 12. Replace version-specific parts of the compat_netbsd32 module (and also the compat_netbsd32_sysv module) with individual modules. Update dependencies accordingly. (Done, but see #13 below.) 13. Finished splitting the vnd_30 and vnd_50 compat code into separate modules. 14. Cleaned up some previous vectored routines (related to if_43.c) to use the MP-safe mechanism. TODO - Required for branch merge -------------------------------- 15. Need to finish cleaning up the netbsd32 machine-dependent code, since the MI code assumes that there's MD file available. 16. The ieee_80211 compat code needs to be verified to make sure it is handling the if43_20 compat routine cvtcmd() correctly. 17. There are a few function pointers in netbsd32 module that need to be converted to the new MP-safe mechanism. See files netbsd32_mod.c netbsd32_module.c netbsd32_compat_80.[ch] amd64's machdep.c and machdep_16.c 18. Need to untangle the machdep COREDUMP stuff. TODO - Not required for branch merge ------------------------------------ 19. Audit the entire code base for any remaining embedded #ifdef's for COMPAT_xx. When found, move the actual compat code into the compat hierarchy and replace originals with indirect (vectored) calls. 20. The rtsock compat code is a disaster, with rtsock_50.c #include-ing the main rtsock.c code with various manipulations of the COMPAT_50 macro. Once rtsock is separated, compat_14 references to rtsock_50 routines needs to be verified. Currently, this entire code is built for the monolithic COMPAT module, but there's no way to reach the entry points, so none of the compat code can be executed, neither on the branch nor on HEAD. 21. The compat_60 module still needs some work for XEN systems. We probably need some build infrastructure changes to ensure that XEN (and, for i386, XEN-PAE) modules are build with the correct macros defined and with -I directories specified in the same order as for building kernels. See PR port-xen/53130. This currently prevents loading of micro-code updates for amd64 processors running XEN kernels. This limitation also exists on HEAD. 22. There seems to be quite a bit of MD compat_xx code, in the various sys/arch/ directories. I haven't yet looked at any of this. But it seems to me that the MI compat build infrastructure should have some mechanism to "reach over" to the MD code, #include a Makefile.inc file, and perhaps define something to enable the MI modcmd code to call a compat_xx_MD_init() routine. Note also that there are a few bits of MD code that is COMPAT_44 related. (The only bit of MI COMPAT_44 code is in the single module shared by COMPAT_43 and COMPAT_09.) This affects the cesfic, hp300, news68k, and x68k platforms, all in their respective machdep.c source file. Additionally, the zaurus platform defines COMPAT_44 in its INSTALL kernel configuration - but no other configuration files! As far as I can tell, none of the MD compat code is currently built into the monolithic COMPAT module on HEAD. Thus, its absence from any of the version-specific modules is not a regression. 23. For compat_50, in addition to rtsock there are some things in dev/gpio and dev/wscons/wsmux that I haven't been able to cleanly separate. These items are not currently included in the monolithic COMPAT module on HEAD, so lack of integration on the branch is not a regression.