All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Thorsten Leemhuis <linux@leemhuis.info>,
	Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: [PATCH v3] docs: describe how to quickly build a trimmed kernel
Date: Mon, 6 Mar 2023 11:19:54 +0700	[thread overview]
Message-ID: <ZAVp6jdeWzYcisUO@debian.me> (raw)
In-Reply-To: <1a788a8e7ba8a2063df08668f565efa832016032.1678021408.git.linux@leemhuis.info>

[-- Attachment #1: Type: text/plain, Size: 1757 bytes --]

On Sun, Mar 05, 2023 at 02:04:44PM +0100, Thorsten Leemhuis wrote:
> + * Create the build configuration for your kernel based on an existing
> +   configuration.
> +
> +   If you already prepared such a '.config' file yourself, copy it to
> +   ~/linux/ and run ``make olddefconfig``.
> +
> +   Use the same command, if your distribution or somebody else already tailored
> +   your running kernel to your or your hardware's needs: the make target
> +   'olddefconfig' will then try to use that kernel's .config as base.
> +
> +   Using this make target is fine for everybody else, too -- but you often can
> +   save a lot of time by using this command instead::
> +
> +     yes "" | make localmodconfig
> +
> +   This will try to pick your distribution's kernel as base, but then disable
> +   modules for any features apparently superfluous for your setup. This will
> +   reduce the compile time enormously, especially if you are running an
> +   universal kernel from a commodity Linux distribution.
> +
> +   There is a catch: the make target 'localmodconfig' will disable kernel
> +   features you have not directly or indirectly through some program utilized
> +   since you booted the system. You can reduce or nearly eliminate that risk by
> +   using tricks outlined in the reference section; for quick testing purposes
> +   that risk is often negligible, but it is an aspect you want to keep in mind
> +   in case your kernel behaves oddly.

If your distro config have ``CONFIG_IKCONFIG=y``, you can copy from
procfs::

    zcat /proc/config.gz > .config

If it isn't the case, you may want to enable the aforementioned config
option.

Thanks. 

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2023-03-06  4:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 13:04 [PATCH v3] docs: describe how to quickly build a trimmed kernel Thorsten Leemhuis
2023-03-06  4:14 ` Bagas Sanjaya
2023-03-06  6:03   ` Thorsten Leemhuis
2023-03-06  4:19 ` Bagas Sanjaya [this message]
2023-03-06  5:40   ` Thorsten Leemhuis
2023-03-06  8:57     ` Bagas Sanjaya
2023-03-06  9:07       ` Thorsten Leemhuis
2023-03-07  2:57         ` Bagas Sanjaya
2023-03-09 14:42 ` Greg KH
2023-03-14 18:35 ` Jonathan Corbet
2023-03-15  4:17   ` Bagas Sanjaya
2023-03-15  9:28   ` Thorsten Leemhuis
2023-03-16 18:27     ` Jonathan Corbet
2023-03-22 13:47       ` Thorsten Leemhuis
2023-03-23 17:24         ` Jonathan Corbet
2023-03-23 17:37           ` Thorsten Leemhuis
2023-03-23 18:08             ` Jonathan Corbet
2023-03-15  4:19 ` Bagas Sanjaya

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=ZAVp6jdeWzYcisUO@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=lukas.bulwahn@gmail.com \
    --cc=rdunlap@infradead.org \
    --cc=regressions@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.