linux-kernel - Re: [PATCH] arm64: defconfig: Enable Qualcomm interconnects as built-in

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <78f6091c-1630-48c2-93e6-71f2cdbe63c5@kernel.org>
Date: Wed, 12 Mar 2025 09:54:14 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Christopher Obbard <christopher.obbard@...aro.org>,
 Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>,
 Bjorn Andersson <andersson@...nel.org>,
 Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
 linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH] arm64: defconfig: Enable Qualcomm interconnects as
 built-in

On 11/03/2025 19:02, Christopher Obbard wrote:
> Currently some Qualcomm interconnect drivers are enabled
> as modules which isn't overly useful since the interconnects
> are required to be loaded during early boot.
> 
> Loading the interconnects late (e.g. in initrd or as module)
> can cause boot issues, such as slowdown or even not booting
> at all (since the interconnect would be required for storage
> devices).
> 
> Be consistent and enable all of the Qualcomm interconnect
> drivers as built-in to the kernel image.


I don't agree. If you want consistency, fix booting process and make
everything module. We switch them to builtin on exception, so come with
reasoning for given exceptions instead of making exceptions the new normal.

Best regards,
Krzysztof