Linux-Modules Archive on
 help / color / Atom feed
From: Jessica Yu <>
To: Alexey Gladkov <>
Cc: Masahiro Yamada <>,
	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 v3] moduleparam: Save information about built-in modules in separate file
Date: Mon, 29 Apr 2019 16:21:56 +0200
Message-ID: <20190429142156.GA31567@linux-8ccs> (raw)
In-Reply-To: <>

+++ Alexey Gladkov [29/04/19 11:08 +0200]:
>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.
>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


Otherwise, for module.h and moduleparam.h:

Acked-by: Jessica Yu <>

And it would be great if Lucas can confirm if the file format and name
would be OK for kmod.



  reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-29  9:08 Alexey Gladkov
2019-04-29 14:21 ` Jessica Yu [this message]
2019-04-29 15:08 ` Masahiro Yamada
2019-04-29 15:35   ` Alexey Gladkov

Reply instructions:

You may reply publically 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=20190429142156.GA31567@linux-8ccs \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Modules Archive on

Archives are clonable:
	git clone --mirror linux-modules/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-modules linux-modules/ \
	public-inbox-index linux-modules

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox