Messages in this thread | | | From | Andi Kleen <> | Subject | Re: [PATCH v1] moduleparam: Save information about built-in modules in separate file | Date | Wed, 06 Mar 2019 16:07:03 -0800 |
| |
Alexey Gladkov <gladkov.alexey@gmail.com> writes:
> Problem: > > When a kernel module is compiled as a separate module, some important > information about the kernel module is available via .modinfo section of > the module. In contrast, when the kernel module is compiled into the > kernel, that information is not available. > > Information about built-in modules is necessary in the following cases: > > 1. When it is necessary to find out what additional parameters can be > passed to the kernel at boot time. > > 2. When you need to know which module names and their aliases are in > the kernel. This is very useful for creating an initrd image.
I would just keep it in the vmlinux as a non loadable segment, which won't make it into bzImage. vmlinux passed around anyways, and it's easier to handle than extra files, and it already has plenty of metadata in it.
-Andi
| |