On January 19, 2019 2:36:06 AM PST, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: >On Sat, Jan 19, 2019 at 02:28:00AM -0800, Christoph Hellwig wrote: >> This seems like a pretty horrible idea and waste of kernel memory. > >It's only a waste if you want it to be a waste, i.e. if you load the >kernel module. > >This really isn't any different from how /proc/config.gz works. > >> Just add support to kbuild to store a compressed archive in initramfs >> and unpack it in the right place. > >I think the issue is that some devices do not use initramfs, or switch >away from it after init happens or something like that. Joel has all >of >the looney details that he can provide. > >thanks, > >greg k-h Yeah, well... but it is kind of a losing game... the more in-kernel stuff there is the less smiley are things to actually be supported. Modularizing is it in some ways even crazier in the sense that at that point you are relying on the filesystem containing the module, which has to be loaded into the kernel by a root user. One could even wonder if a better way to do this would be to have "make modules_install" park an archive file – or even a directory as opposed to a symlink – with this stuff in /lib/modules. We could even provide a tmpfs shim which autoloads such an archive via the firmware loader; this might even be generically useful, who knows. Note also that initramfs contents can be built into the kernel. Extracting such content into a single-instance tmpfs would again be a possibility. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
