archive mirror
 help / color / mirror / Atom feed
From: Jessica Yu <>
To: Masahiro Yamada <>
Cc: Alexey Gladkov <>,
	Linux Kernel Mailing List <>,
	Linux Kbuild mailing list <>,,,
	"Kirill A . Shutemov" <>,
	Gleb Fotengauer-Malinovskiy <>,
	"Dmitry V. Levin" <>,
	Michal Marek <>,
	Dmitry Torokhov <>,
	Rusty Russell <>,
	Lucas De Marchi <>
Subject: Re: [PATCH v2] moduleparam: Save information about built-in modules in separate file
Date: Thu, 18 Apr 2019 15:52:38 +0200	[thread overview]
Message-ID: <20190418135238.GA5626@linux-8ccs> (raw)
In-Reply-To: <>

+++ Masahiro Yamada [18/04/19 20:10 +0900]:
>On Sat, Apr 6, 2019 at 9:15 PM Alexey Gladkov <> wrote:
>> 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.
>> Proposal:
>> The proposed patch does not remove .modinfo section with module
>> information from the vmlinux at the build time and saves it into a
>> separate file after kernel linking. So, the kernel does not increase in
>> size and no additional information remains in it. Information is stored
>> in the same format as in the separate modules (null-terminated string
>> array). Because the .modinfo section is already exported with a separate
>> modules, we are not creating a new API.
>> It can be easily read in the userspace:
>> $ tr '\0' '\n' < kernel.builtin
>> ext4.softdep=pre: crc32c
>> ext4.license=GPL
>> ext4.description=Fourth Extended Filesystem
>> Card, Stephen Tweedie, Andrew Morton, Andreas Dilger, Theodore Ts'o and others
>> ext4.alias=fs-ext4
>> ext4.alias=ext3
>> ext4.alias=fs-ext3
>> ext4.alias=ext2
>> ext4.alias=fs-ext2
>> md_mod.alias=block-major-9-*
>> md_mod.alias=md
>> md_mod.description=MD RAID framework
>> md_mod.license=GPL
>> md_mod.parmtype=create_on_open:bool
>> md_mod.parmtype=start_dirty_degraded:int
>> ...
>> v2:
>>  * Extract modinfo from vmlinux.o as suggested by Masahiro Yamada;
>>  * Rename output file to kernel.builtin;
>Sorry, I do not get why you renamed
>"kernel.builtin.modinfo" to "kernel.builtin".
>If you drop "modinfo", we do not understand
>what kind information is contained in it.
>I think "kernel" and "builtin" have
>a quite similar meaning here.
>How about "builtin.modinfo" for example?
>It is shorter, and it is clear enough
>that it contains module_info.

I agree that the name kernel.builtin is unclear in what kind of
information it contains. Apologies for not having clarified this in
the previous review.

Since kbuild already produces "modules.order" and "modules.builtin"
files, why not just name it "modules.builtin.modinfo" to keep the
names consistent with what is already there? It clearly conveys that
this file contains modinfo for builtin modules.

I'll leave it up to Lucas to decide if the file format is OK for kmod.
With the modinfo dump, kmod could then decide what to do with the
information, append to modules.alias{,.bin}, etc.

Also, I think this file needs to be documented in Documentation/kbuild/kbuild.txt.



  reply	other threads:[~2019-04-18 13:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-06 12:14 [PATCH v2] moduleparam: Save information about built-in modules in separate file Alexey Gladkov
2019-04-18 11:10 ` Masahiro Yamada
2019-04-18 13:52   ` Jessica Yu [this message]
2019-04-18 14:36     ` Lucas De Marchi
2019-04-18 15:26     ` Masahiro Yamada
2019-04-18 15:36       ` Jessica Yu
2019-04-19  3:03         ` Masahiro Yamada
2019-04-26 15:29           ` Alexey Gladkov
2019-04-29  3:28             ` Masahiro Yamada

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:

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

  git send-email \
    --in-reply-to=20190418135238.GA5626@linux-8ccs \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).