From: Julian Braha <julianbraha@gmail.com>
To: "Ahmed S. Darwish" <darwi@linutronix.de>
Cc: "Clark Williams" <clrkwllms@kernel.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nsc@kernel.org>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Frederic Weisbecker" <frederic@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"John Ogness" <john.ogness@linutronix.de>,
"Derek Barbosa" <debarbos@redhat.com>,
"Zbigniew Jędrzejewski-Szmek" <zbyszek@amutable.com>,
"Daan De Meyer" <daan.j.demeyer@gmail.com>,
"Luca Boccassi" <luca.boccassi@gmail.com>,
linux-rt-devel@lists.linux.dev, debian-kernel@lists.debian.org,
linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, arighi@nvidia.com
Subject: Re: [PATCH v1 00/10] tools: Introduce a kernel configuration checker
Date: Tue, 10 Nov 2026 18:18:54 +0000 [thread overview]
Message-ID: <c0ccddbc-539c-4987-8685-ec996285f746@gmail.com> (raw)
In-Reply-To: <avHroNa1vcxmCIOs@lx-t490>
[-- Attachment #1.1: Type: text/plain, Size: 2307 bytes --]
On 11/9/26 15:49, Ahmed S. Darwish wrote:
> Hi Julian,
>
> On Sun, 08 Nov 2026, Julian Braha wrote:
>> Cool tool 🙂
>>
> Thanks!
>
>>> If no ruleset is specified, the target prints the available rulesets:
>>>
>>> $ make checkconfig
>>> Usage: make RULES=<profile> [OVERLAY=<overlay>] checkconfig
>>> Available RULES: preempt_rt
>>>
>>> The overlay mechanism allows distributions, CI systems, and Board Support
>> On the topic of distributions, this seems *a lot* like Canonical's
>> Annotations [1], albeit yours uses YAML and supports matching option
>> names with regex.
> The difference is not only in the implementation details. Please see below.
>
>> As you say about PREEMPT_RT configuration not being
>> "one-size-fits-all", similarly there are 100+ Ubuntu kernels that need
>> to adhere to a configuration "policy".
>>
>> So this seems to be a real problem that others are having.
>>
> Kernel configuration is definitely getting trickier. That's why I've
> contributed the PREEMPT_RT kernel configuration guide earlier:
>
> https://docs.kernel.org/core-api/real-time/kernel-configuration.html
>
> Regarding the Canonical tool, it's the first time I see it. From that
> announce e-mail, it seems that they're using it for generating a .config:
>
> Starting with 22.04 (Jammy Jellyfish), Ubuntu kernels are now using
> only annotations to /generate/ their corresponding .config.
>
> ...
>
> $ ./debian/scripts/misc/annotations --arch amd64 --flavour generic > .config
>
> Yocto also provides a very light concept of .config generation:
>
> https://docs.yoctoproject.org/kernel-dev/common.html#creating-
> configuration-fragments
>
> But this tool does not conern itself with generation. That is, Canonical
> can use this tool to validate that they've generated the right thing! 😉
Yeah, Annotations also supports generation with --export.
But it does support validating a config with a policy using --check [1]
Anyway, the point was to provide context for the maintainers that this
problem is bigger than PREEMPT_RT. I want to see this functionality /
your tool in upstream.
[1]
https://git.launchpad.net/~arighi/+git/annotations-tools/tree/kconfig/run.py?h=main#n117
- Julian Braha
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2026-11-10 18:18 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 9:19 Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 01/10] kconfig-checker: Add schema for rule files Ahmed S. Darwish
2026-11-08 18:59 ` Julian Braha
2026-11-09 12:40 ` Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 02/10] kconfig-checker: Introduce PREEMPT_RT configuration rules Ahmed S. Darwish
2026-11-07 9:20 ` sashiko-bot
2026-11-09 18:09 ` Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 03/10] kconfig-checker: Add the configuration checker code Ahmed S. Darwish
2026-11-07 9:20 ` sashiko-bot
2026-11-09 19:29 ` Ahmed S. Darwish
2026-11-08 18:59 ` Julian Braha
2026-11-09 13:00 ` Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 04/10] kconfig: Introduce checkconfig target Ahmed S. Darwish
2026-11-07 9:20 ` sashiko-bot
2026-11-09 20:07 ` Ahmed S. Darwish
2026-11-08 18:59 ` Julian Braha
2026-11-09 0:39 ` Nathan Chancellor
2026-11-09 13:18 ` Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 05/10] Documentation: Describe kconfig-checker usage and design Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 06/10] kconfig-checker: Split schema to support component reuse Ahmed S. Darwish
2026-11-07 9:20 ` sashiko-bot
2026-11-09 18:22 ` Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 07/10] kconfig-checker: Introduce overlays schema Ahmed S. Darwish
2026-11-07 9:20 ` sashiko-bot
2026-11-09 16:47 ` Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 08/10] kconfig-checker: Add support for rule overlays Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 09/10] Documentation: Describe kconfig-checker overlays Ahmed S. Darwish
2026-11-07 9:20 ` sashiko-bot
2026-11-09 16:50 ` Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 10/10] kconfig: Introduce OVERLAY= for make checkconfig Ahmed S. Darwish
2026-11-08 18:59 ` [PATCH v1 00/10] tools: Introduce a kernel configuration checker Julian Braha
2026-11-09 0:37 ` Nathan Chancellor
2026-11-09 16:15 ` Ahmed S. Darwish
2026-11-09 16:52 ` Nathan Chancellor
2026-11-09 17:04 ` Ahmed S. Darwish
2026-11-09 15:49 ` Ahmed S. Darwish
2026-11-10 18:18 ` Julian Braha [this message]
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=c0ccddbc-539c-4987-8685-ec996285f746@gmail.com \
--to=julianbraha@gmail.com \
--cc=arighi@nvidia.com \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=corbet@lwn.net \
--cc=daan.j.demeyer@gmail.com \
--cc=darwi@linutronix.de \
--cc=debarbos@redhat.com \
--cc=debian-kernel@lists.debian.org \
--cc=frederic@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=luca.boccassi@gmail.com \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=rostedt@goodmis.org \
--cc=zbyszek@amutable.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®