From: Yoann Congal <yoann.congal@smile.fr>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Vegard Nossum <vegard.nossum@oracle.com>
Subject: Re: [PATCH 1/2] kconfig: remove unneeded symbol_empty variable
Date: Tue, 23 Jan 2024 16:11:04 +0100 [thread overview]
Message-ID: <d21298d9-fed6-4e08-9780-dbcb388b9ccc@smile.fr> (raw)
In-Reply-To: <CAMuHMdWm6u1wX7efZQf=2XUAHascps76YQac6rdnQGhc8nop_Q@mail.gmail.com>
Le 23/01/2024 à 13:54, Geert Uytterhoeven a écrit :
> Hi Yamada-san,
Hello,
> On Sat, Nov 25, 2023 at 5:36 PM Masahiro Yamada <masahiroy@kernel.org> wrote:
>> This is used only for initializing other variables.
>>
>> Use the empty string "".
>>
>> Please note newval.tri is unused for S_INT/HEX/STRING.
>>
>> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
>
> Thanks for your patch, which is now commit 4e244c10eab345a7
> ("kconfig: remove unneeded symbol_empty variable") in v6.8-rc1.
>
> When running "make <foo>_defconfig" with <foo>_defconfig an SMP
> defconfig without explicit configuration of CONFIG_LOG_CPU_MAX_BUF_SHIFT,
> the aforementioned commit causes a change in the generated .config:
>
> -CONFIG_LOG_CPU_MAX_BUF_SHIFT=12
> +CONFIG_LOG_CPU_MAX_BUF_SHIFT=0
>
> It looks like CONFIG_BASE_SMALL=0 is treated as a string instead of
> the integer number zero?
>
> init/Kconfig=config LOG_CPU_MAX_BUF_SHIFT
> init/Kconfig- int "CPU kernel log buffer size contribution (13 => 8
> KB, 17 => 128KB)"
> init/Kconfig- depends on SMP
> init/Kconfig- range 0 21
> init/Kconfig: default 12 if !BASE_SMALL
> init/Kconfig: default 0 if BASE_SMALL
>
> Note that reverting 4e244c10eab345a7 is not sufficient to fix the issue.
> Also reverting commit 6262afa10ef7cc8f ("kconfig: default to zero if
> int/hex symbol lacks default property") does fix it.
(Since I'd really like 6262afa10ef7cc8f ("kconfig: default to zero if int/hex symbol lacks default property") to stay, allow me to try to help)
The problem is quite easy to reproduce:
$ make x86_64_defconfig
$ grep 'LOG_CPU_MAX_BUF_SHIFT\|BASE_SMALL\|BASE_FULL' .config
CONFIG_LOG_CPU_MAX_BUF_SHIFT=0
CONFIG_BASE_FULL=y
CONFIG_BASE_SMALL=0
Here, CONFIG_LOG_CPU_MAX_BUF_SHIFT should be 12 not 0.
For what it is worth, CONFIG_BASE_SMALL is defined as an int but is only used as a bool :
$ git grep BASE_SMALL
arch/x86/include/asm/mpspec.h:#if CONFIG_BASE_SMALL == 0
drivers/tty/vt/vc_screen.c:#define CON_BUF_SIZE (CONFIG_BASE_SMALL ? 256 : PAGE_SIZE)
include/linux/threads.h:#define PID_MAX_DEFAULT (CONFIG_BASE_SMALL ? 0x1000 : 0x8000)
include/linux/threads.h:#define PID_MAX_LIMIT (CONFIG_BASE_SMALL ? PAGE_SIZE * 8 : \
include/linux/udp.h:#define UDP_HTABLE_SIZE_MIN (CONFIG_BASE_SMALL ? 128 : 256)
include/linux/xarray.h:#define XA_CHUNK_SHIFT (CONFIG_BASE_SMALL ? 4 : 6)
init/Kconfig: default 12 if !BASE_SMALL
init/Kconfig: default 0 if BASE_SMALL
init/Kconfig:config BASE_SMALL
kernel/futex/core.c:#if CONFIG_BASE_SMALL
kernel/user.c:#define UIDHASH_BITS (CONFIG_BASE_SMALL ? 3 : 7)
Maybe we should change CONFIG_BASE_SMALL to the bool type?
I'll poke around to see if I can understand why a int="0" is true for kconfig.
Regards,
--
Yoann Congal
Smile ECS - Tech Expert
next prev parent reply other threads:[~2024-01-23 15:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 16:35 Masahiro Yamada
2023-11-25 16:35 ` [PATCH 2/2] kconfig: default to zero if int/hex symbol lacks default property Masahiro Yamada
2023-11-25 23:10 ` Yoann Congal
2024-01-23 12:54 ` [PATCH 1/2] kconfig: remove unneeded symbol_empty variable Geert Uytterhoeven
2024-01-23 15:11 ` Yoann Congal [this message]
2024-01-24 8:09 ` Masahiro Yamada
2024-01-24 8:56 ` Yoann Congal
2024-01-24 20:12 ` Masahiro Yamada
2024-01-25 14:42 ` Yoann Congal
2024-01-26 13:20 ` Masahiro Yamada
2024-01-25 14:48 ` Geert Uytterhoeven
2024-01-24 9:52 ` Geert Uytterhoeven
2024-01-24 11:43 ` Masahiro Yamada
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=d21298d9-fed6-4e08-9780-dbcb388b9ccc@smile.fr \
--to=yoann.congal@smile.fr \
--cc=geert@linux-m68k.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=vegard.nossum@oracle.com \
/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
all inboxes | Powered by JetHome®