TODO.compat-module revision 1.1.2.12
1 /* $NetBSD: TODO.compat-module,v 1.1.2.12 2018/09/25 21:44:30 pgoyette Exp $ */ 2 3 DONE 4 ---- 5 1. Removed the building of the compat library - it is no longer needed. 6 7 2. Reverted some intentional auto-load breakage for loading the sysv_ipc 8 module; the breakage was introduced as the fix for the above-mentioned 9 build breakage. 10 11 3. Split the sysv_ipc compat routines into their own compat_sysv module. 12 13 4. Resolved some inter-module dependencies. 14 15 5. Extracted some net/if.c compat routines into the compat module, and 16 replaced the originals with indirect (vectored) function calls. 17 18 6. Reconfirmed existing compat-module dependencies, and update the 19 defopt/defflag lines in the config files* as needed, to insure that 20 built-in dependencies get resolved. 21 22 7. Fixed limits on the number of module depedencies and maximum 23 recursion level have been removed. Previous code for reporting 24 module status to userland has been versioned and moved to the 25 compat_80 module. 26 27 8. The old monolithic compat module has been broken into multiple 28 modules, one for each old NetBSD version. The monolithic module 29 is no longer available. 30 31 Similarly, the compat_sysv module has also been split into several 32 version-specific modules, and the mini-monolithic compat_sysv module 33 is no longer provided. 34 35 9. syscalls.master has been updated to autoload the version-specific 36 compat modules rather than the monolithic modules. 37 38 10. Separated COMPAT_BSDPTY stuff, allowing the COMPAT_60 module to be 39 built regardless. 40 41 11. Implemented a MP-safe mechanism for installing and removing function 42 pointers. Thanks to riastradh@ for the template code. 43 44 12. Replace version-specific parts of the compat_netbsd32 module (and 45 also the compat_netbsd32_sysv module) with individual modules. Update 46 dependencies accordingly. (Done, but see #13 below.) 47 48 13. Finished splitting the vnd_30 and vnd_50 compat code into separate 49 modules. 50 51 14. Cleaned up some previous vectored routines (related to if_43.c) to 52 use the MP-safe mechanism. 53 54 55 TODO - Required for branch merge 56 -------------------------------- 57 15. Need to finish cleaning up the netbsd32 machine-dependent code, since 58 the MI code assumes that there's MD file available. 59 60 16. The ieee_80211 compat code needs to be verified to make sure it is 61 handling the if43_20 compat routine cvtcmd() correctly. 62 63 17. There are a few function pointers in netbsd32 module that need to 64 be converted to the new MP-safe mechanism. See files 65 netbsd32_mod.c 66 netbsd32_module.c 67 netbsd32_compat_80.[ch] 68 amd64's machdep.c and machdep_16.c 69 70 18. Need to untangle the machdep COREDUMP stuff. 71 72 73 TODO - Not required for branch merge 74 ------------------------------------ 75 19. Audit the entire code base for any remaining embedded #ifdef's for 76 COMPAT_xx. When found, move the actual compat code into the compat 77 hierarchy and replace originals with indirect (vectored) calls. 78 79 20. The rtsock compat code is a disaster, with rtsock_50.c #include-ing 80 the main rtsock.c code with various manipulations of the COMPAT_50 81 macro. Once rtsock is separated, compat_14 references to rtsock_50 82 routines needs to be verified. 83 84 Currently, this entire code is built for the monolithic COMPAT 85 module, but there's no way to reach the entry points, so none of 86 the compat code can be executed, neither on the branch nor on 87 HEAD. 88 89 21. The compat_60 module still needs some work for XEN systems. We 90 probably need some build infrastructure changes to ensure that 91 XEN (and, for i386, XEN-PAE) modules are build with the correct 92 macros defined and with -I directories specified in the same order 93 as for building kernels. See PR port-xen/53130. This currently 94 prevents loading of micro-code updates for amd64 processors running 95 XEN kernels. This limitation also exists on HEAD. 96 97 22. There seems to be quite a bit of MD compat_xx code, in the various 98 sys/arch/ directories. I haven't yet looked at any of this. But it 99 seems to me that the MI compat build infrastructure should have some 100 mechanism to "reach over" to the MD code, #include a Makefile.inc file, 101 and perhaps define something to enable the MI modcmd code to call a 102 compat_xx_MD_init() routine. 103 104 Note also that there are a few bits of MD code that is COMPAT_44 105 related. (The only bit of MI COMPAT_44 code is in the single module 106 shared by COMPAT_43 and COMPAT_09.) This affects the cesfic, hp300, 107 news68k, and x68k platforms, all in their respective machdep.c 108 source file. Additionally, the zaurus platform defines COMPAT_44 in 109 its INSTALL kernel configuration - but no other configuration files! 110 111 As far as I can tell, none of the MD compat code is currently built 112 into the monolithic COMPAT module on HEAD. Thus, its absence from 113 any of the version-specific modules is not a regression. 114 115 23. For compat_50, in addition to rtsock there are some things in dev/gpio 116 and dev/wscons/wsmux that I haven't been able to cleanly separate. 117 These items are not currently included in the monolithic COMPAT module 118 on HEAD, so lack of integration on the branch is not a regression. 119 120
Indexes created Sat May 16 00:24:39 UTC 2026