[PATCH] arm64: defconfig: Disable DEBUG_INFO

[Will Deacon]

On Tue, Mar 02, 2021 at 06:58:52PM +0000, Mark Brown wrote:
> We've had DEBUG_INFO enabled for arm64 defconfigs since the initial
> commit.  This is probably not that frequently used but substantially
> inflates the size of the build tree and amount of I/O needed during the
> build.  This was causing issues with storage usage in some automated CI
> environments which don't expect defconfigs to be quite this big, and
> generally increases the resource consumption for both them and people
> doing local builds.  Turn the option off by default to remove these
> overheads from the default, people can always enable DEBUG_INFO if they
> need it.
> 
> Without this patch my build tree is 6.8G, with it the size drops to 909M.
> 
> Reported-by: Guillaume Tucker <guillaume.tucker at collabora.com>
> Signed-off-by: Mark Brown <broonie at kernel.org>
> Cc: Kevin Hilman <khilman at baylibre.com>
> ---
>  arch/arm64/configs/defconfig | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index d612f633b771..c246dfc0a175 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -1155,7 +1155,6 @@ CONFIG_CRYPTO_DEV_HISI_HPRE=m
>  CONFIG_CRYPTO_DEV_HISI_TRNG=m
>  CONFIG_CMA_SIZE_MBYTES=32
>  CONFIG_PRINTK_TIME=y
> -CONFIG_DEBUG_INFO=y
>  CONFIG_MAGIC_SYSRQ=y
>  CONFIG_DEBUG_FS=y
>  CONFIG_DEBUG_KERNEL=y

Hmm. Doing this means ./scripts/faddr2line no longer works with the vmlinux,
which means if somebody forgets to enable DEBUG_INFO they're in for a
really hard time debugging when something goes wrong.

Why can't the CI systems just disable DEBUG_INFO themselves instead of
changing defconfig for everybody?

Will