From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 05 May 2026 13:34:00 +0200 Received: from metis.whiteo.stw.pengutronix.de ([2a0a:edc0:2:b01:1d::104]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wKE2L-001EAx-0l for lore@lore.pengutronix.de; Tue, 05 May 2026 13:34:00 +0200 Received: from [127.0.0.1] (helo=metis.whiteo.stw.pengutronix.de) by metis.whiteo.stw.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1wKE2J-0006IJ-Pt; Tue, 05 May 2026 13:33:59 +0200 Received: from ptz.office.stw.pengutronix.de ([2a0a:edc0:0:900:1d::77] helo=[127.0.0.1]) by metis.whiteo.stw.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1wKE2G-0006HI-OM; Tue, 05 May 2026 13:33:56 +0200 Message-ID: Date: Tue, 5 May 2026 13:33:56 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Lucas Stach , distrokit@pengutronix.de References: <20260505111714.1361551-1-l.stach@pengutronix.de> From: Ahmad Fatoum Content-Language: en-US, de-DE, de-BE In-Reply-To: <20260505111714.1361551-1-l.stach@pengutronix.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [DistroKit] [PATCH v3 1/4] x86_64: kernel: update config X-BeenThere: distrokit@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: DistroKit Mailinglist List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "DistroKit" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: distrokit-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.whiteo.stw.pengutronix.de); SAEximRunCond expanded to false 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 |