Home | History | Annotate | Line # | Download | only in doc
TODO.compat-module revision 1.1.2.24 
      1 /* $NetBSD: TODO.compat-module,v 1.1.2.24 2019/01/18 05:42:34 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 dependencies 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     (new) 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 #19 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 15. Organized (some of) the netbsd32 machine-dependent code to fit a
     55     common build framework, and split version-specific code from baseline
     56     code as needed.
     57 
     58 16. The rtsock.c code has been split into two separate source files,
     59     one for use in -current and one which is shared with COMPAT_50 (the
     60     code is shared with -current, but macros are used to define version-
     61     specific routine names and variable types).
     62 
     63 TODO - Not required for branch merge
     64 ------------------------------------
     65 17. Audit the entire code base for any remaining embedded #ifdef's for
     66     COMPAT_xx.  When found, move the actual compat code into the compat
     67     hierarchy and replace originals with indirect (vectored) calls.
     68 
     69 18. The compat_60 module still needs some work for XEN systems.  We
     70     probably need some build infrastructure changes to ensure that
     71     XEN (and, for i386, XEN-PAE) modules are build with the correct
     72     macros defined and with -I directories specified in the same order
     73     as for building kernels. See PR port-xen/53130.  This currently
     74     prevents loading of micro-code updates for amd64 processors running
     75     XEN kernels.  This limitation also exists on HEAD.
     76 
     77 19. There seems to be quite a bit of MD compat_xx code, in the various
     78     sys/arch/ directories.  I haven't yet looked at any of this.  But it
     79     seems to me that the MI compat build infrastructure should have some
     80     mechanism to "reach over" to the MD code, #include a Makefile.inc file,
     81     and perhaps define something to enable the MI modcmd code to call a
     82     compat_xx_MD_init() routine.
     83 
     84     Note also that there are a few bits of MD code that is COMPAT_44
     85     related.  (The only bit of MI COMPAT_44 code is in the single module
     86     shared by COMPAT_43 and COMPAT_09.)  This affects the cesfic, hp300,
     87     news68k, and x68k platforms, all in their respective machdep.c
     88     source file.  Additionally, the zaurus platform defines COMPAT_44 in
     89     its INSTALL kernel configuration - but no other configuration files!
     90 
     91     As far as I can tell, none of the MD compat code is currently built
     92     into the monolithic COMPAT module on HEAD.  Thus, its absence from
     93     any of the version-specific modules is not a regression.
     94 
     95 20. For compat_50, there are some things in dev/gpio and dev/wscons/wsmux
     96     that I haven't been able to cleanly separate.  These items are not
     97     currently included in the monolithic COMPAT module on HEAD, so lack of
     98     integration on the branch is not a regression.
     99 
    100 21. Find all the remaining dependencies on the compat_utils routines and
    101     deal with them appropriately.  For now, we simply ensure that they
    102     are included in every kernel via 'options COMPAT_UTILS' in file
    103     sys/conf/std
    104 
    105