public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: unlisted-recipients:; (no To-header on input)
Cc: gladkov.alexey@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] moduleparam: Save information about built-in modules in separate file
Date: Wed, 06 Mar 2019 16:07:03 -0800	[thread overview]
Message-ID: <871s3jv97c.fsf@linux.intel.com> (raw)
In-Reply-To: <20190306165425.GD14017@MacBook-PC.fortress> (Alexey Gladkov's message of "Wed, 6 Mar 2019 17:54:25 +0100")

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

  reply	other threads:[~2019-03-07  0:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 16:54 [PATCH v1] moduleparam: Save information about built-in modules in separate file Alexey Gladkov
2019-03-07  0:07 ` Andi Kleen [this message]
2019-03-07 11:27   ` Alexey Gladkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871s3jv97c.fsf@linux.intel.com \
    --to=ak@linux.intel.com \
    --cc=gladkov.alexey@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox