[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a5d07fee-b950-ea48-c480-dd5a8a575969@infradead.org>
Date: Fri, 25 Aug 2023 12:11:28 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Kees Cook <keescook@...omium.org>
Cc: Masahiro Yamada <masahiroy@...nel.org>, x86@...nel.org,
linux-arm-kernel@...ts.infradead.org,
linuxppc-dev@...ts.ozlabs.org, linux-riscv@...ts.infradead.org,
linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-kbuild@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH] kbuild: Show Kconfig fragments in "help"
On 8/25/23 11:20, Kees Cook wrote:
> On Thu, Aug 24, 2023 at 05:04:02PM -0700, Randy Dunlap wrote:
>> Hi Kees,
>>
>> On 8/24/23 15:36, Kees Cook wrote:
>>> Doing a "make help" would show only hard-coded Kconfig targets and
>>> depended on the archhelp target to include ".config" targets. There was
>>> nothing showing global kernel/configs/ targets. Solve this by walking
>>> the wildcard list and include them in the output, using the first comment
>>> line as the help text.
>>>
>>> Update all Kconfig fragments to include help text and adjust archhelp
>>> targets to avoid redundancy.
>>>
>>> Adds the following section to "help" target output:
>>>
>>> Configuration fragment targets (for enabling various Kconfig items):
>>> debug.config - Debugging for CI systems and finding regressions
>>> kvm_guest.config - Bootable as a KVM guest
>>> nopm.config - Disable Power Management
>>> rust.config - Enable Rust
>>> tiny-base.config - Minimal options for tiny systems
>>> tiny.config - Smallest possible kernel image
>>> x86_debug.config - Debugging options for tip tree testing
>>> xen.config - Bootable as a Xen guest
>>> tiny.config - x86-specific options for a small kernel image
>>> xen.config - x86-specific options for a Xen virtualization guest
>>
>> ISTM that you are missing the "why" part of this change in the commit
>> description.
>
> I want to see what fragments are available without needing to know the
> source tree layout for their locations. :)
Why? :)
but you don't have to answer. I acquiesce (i.e., give up).
>> "make tinyconfig" is the real target here. The other (tiny.) files are just
>> implementation details.
>> We can't put all implementation details into help messages and it's not
>> difficult to find that the (tiny.) config files are merged to make the
>> final .config file.
>
> Yeah, this seems true for much of the ppc stuff to, as pointed out by
> mpe. I'll go answer there...
>
--
~Randy
Powered by blists - more mailing lists