From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Lucas Stach <l.stach@pengutronix.de>, distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH v3 1/4] x86_64: kernel: update config
Date: Tue, 5 May 2026 13:33:56 +0200 [thread overview]
Message-ID: <b7c087d5-7314-456d-8aef-127ca9ad5b3d@pengutronix.de> (raw)
In-Reply-To: <20260505111714.1361551-1-l.stach@pengutronix.de>
Hi,
On 5/5/26 1:17 PM, Lucas Stach wrote:
> CONFIG_UTS_NS=y
> -CONFIG_TIME_NS=y
> +# CONFIG_TIME_NS is not set
Just spitballing here: With an eye towards Y2038, do we maybe want to
keep this enabled?
- Positive Offset: Enable isolated testing of components with y2038 time
- Negative Offset: Run proprietary components that were't fixed in the past?
> +CONFIG_INITRAMFS_PRESERVE_MTIME=y
FWIW, I normally disable this as this is just extra work that I don't
see the need for in my BSPs.
Quoting 1274aea127b2 ("initramfs: add INITRAMFS_PRESERVE_MTIME Kconfig
option"):
"""
This change adds a new INITRAMFS_PRESERVE_MTIME Kconfig option, which
can be used to disable on-by-default mtime retention and in turn speed
up initramfs extraction, particularly for cpio archives with large
directory counts.
Benchmarks with a one million directory cpio archive extracted 20 times
demonstrated:
mean extraction time (s) std dev
INITRAMFS_PRESERVE_MTIME=y 3.808 0.006
INITRAMFS_PRESERVE_MTIME unset 3.056 0.004
"""
Granted my initramfs are probably not big enough to matter, but still
why do the extra work?
> -CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
> +# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
> # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
> # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
> -# CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL is not set
> +CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL=y
The thinking so far was that performance gives us the best boot time and
then we would switch to a more suitable default from userspace.
Is this outdated practice?
Thanks,
Ahmad
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2026-05-05 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 11:17 Lucas Stach
2026-05-05 11:17 ` [DistroKit] [PATCH v3 2/4] v8a: " Lucas Stach
2026-05-05 11:17 ` [DistroKit] [PATCH v3 3/4] platform-x86_64: switch to ZSTD kernel compression Lucas Stach
2026-05-05 11:17 ` [DistroKit] [PATCH v3 4/4] reason: allow kernel initrd support for all platforms Lucas Stach
2026-05-05 11:33 ` Ahmad Fatoum [this message]
2026-05-06 7:42 ` [DistroKit] [PATCH v3 1/4] x86_64: kernel: update config Michael Olbrich
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=b7c087d5-7314-456d-8aef-127ca9ad5b3d@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=distrokit@pengutronix.de \
--cc=l.stach@pengutronix.de \
/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