[src/trunk]: src/doc Another issue, as identified on IRC/ICB

[pgoyette <pgoyette%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/038d603ed348
branches:  trunk
changeset: 454834:038d603ed348
user:      pgoyette <pgoyette%NetBSD.org@localhost>
date:      Sun Sep 29 00:57:11 2019 +0000

description:
Another issue, as identified on IRC/ICB

diffstat:

 doc/TODO.modules |  11 ++++++++++-
 1 files changed, 10 insertions(+), 1 deletions(-)

diffs (22 lines):

diff -r 0aa98c3c1026 -r 038d603ed348 doc/TODO.modules
--- a/doc/TODO.modules  Sun Sep 29 00:52:26 2019 +0000
+++ b/doc/TODO.modules  Sun Sep 29 00:57:11 2019 +0000
@@ -1,4 +1,4 @@
-/* $NetBSD: TODO.modules,v 1.19 2019/02/20 04:32:51 pgoyette Exp $ */
+/* $NetBSD: TODO.modules,v 1.20 2019/09/29 00:57:11 pgoyette Exp $ */
 
 Some notes on the limitations of our current (as of 7.99.35) module
 subsystem.  This list was triggered by an Email exchange between
@@ -219,3 +219,12 @@
     detail, but I have to wonder how code that compiles cleanly in a
     normal kernel has these issues when compiled in a module, when both
     are done with WARNS=5).
+
+23. The current process of "load all the emulation/exec modules in case
+    one of them might handle the image currently being exec'd" isn't
+    really cool.  (See sys/kern/kern_exec.c?)  It ends up auto-loading
+    a whole bunch of modules, involving file-system access, just to have
+    most of the modules getting unloaded a few seconds later.  We don't
+    have any way to identify which module is needed for which image (ie,
+    we can't determine that an image needs compat_linux vs some other
+    module).