[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z9R2a_dX4YtK4jJ9@google.com>
Date: Fri, 14 Mar 2025 18:33:15 +0000
From: Carlos Llamas <cmllamas@...gle.com>
To: Xiaomeng Zhang <zhangxiaomeng13@...wei.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org,
Boqun Feng <boqun.feng@...il.com>,
"J. R. Okajima" <hooanon05g@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
Waiman Long <longman@...hat.com>, Ingo Molnar <mingo@...hat.com>,
Will Deacon <will@...nel.org>
Subject: Re: [PATCH] lockdep: Fix upper limit for LOCKDEP_BITS configs
On Fri, Mar 14, 2025 at 06:47:29AM +0000, Xiaomeng Zhang wrote:
> The upper limit that was initially setup for LOCKDEP_BITS configs
> is too high (24 bit shift), which causes the kernel image size to exceed
> KERNEL_IMAGE_SIZE (1024MB) limit. When LOCKDEP_BITS is set to 24,
> the kernel image size grows to 1562.19MB.
This is not entirely accurate. Look at _how_ the new upper limits where
determined in commit e638072e6172. This should build just fine:
$ make defconfig
$ ./scripts/config -e PROVE_LOCKING --set-val LOCKDEP_BITS 24
$ make -s olddefconfig all
Is it not the case for you? My guess is that you've also changed _other_
configs and combined with that you hit the limit. If not, can you please
provide the steps and commit you are using?
Thanks,
--
Carlos Llamas
Powered by blists - more mailing lists