From: Randy Dunlap <rdunlap@infradead.org>
To: Kees Cook <keescook@chromium.org>
Cc: linux-s390@vger.kernel.org, linux-kbuild@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org, linux-riscv@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] kbuild: Show Kconfig fragments in "help"
Date: Fri, 25 Aug 2023 12:11:28 -0700 [thread overview]
Message-ID: <a5d07fee-b950-ea48-c480-dd5a8a575969@infradead.org> (raw)
In-Reply-To: <202308251119.B93C95A3A7@keescook>
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
next prev parent reply other threads:[~2023-08-25 19:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 22:36 [PATCH] kbuild: Show Kconfig fragments in "help" Kees Cook
2023-08-25 0:04 ` Randy Dunlap
2023-08-25 18:20 ` Kees Cook
2023-08-25 19:11 ` Randy Dunlap [this message]
2023-08-25 4:56 ` Christophe Leroy
2023-08-25 18:21 ` Kees Cook
2023-08-25 5:44 ` Nicolas Schier
2023-08-25 18:23 ` Kees Cook
2023-08-25 6:11 ` Michael Ellerman
2023-08-25 18:33 ` Kees Cook
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=a5d07fee-b950-ea48-c480-dd5a8a575969@infradead.org \
--to=rdunlap@infradead.org \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=masahiroy@kernel.org \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).