lkml.org 
[lkml]   [2019]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v1] moduleparam: Save information about built-in modules in separate file
On Wed, Mar 06, 2019 at 04:07:03PM -0800, Andi Kleen wrote:
> 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.

Not for all architectures bzImage is created. Also not all distros pack
vmlinux and requiring them to start doing this for a few kilobytes seems
to me wrong.

As follow up I plan to add support of kernel.builtin.modinfo to kmod. The
kmod takes information only from /lib/modules/KVER and does not require the
kernel itself.

--
Rgrds, legion

[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2019-03-07 12:28    [W:0.084 / U:2.200 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site