From: "Ahmed S. Darwish" <darwi@linutronix.de>
To: 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>
Cc: "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,
"Ahmed S. Darwish" <darwi@linutronix.de>
Subject: [PATCH v1 00/10] tools: Introduce a kernel configuration checker
Date: Fri, 6 Nov 2026 10:19:12 +0100 [thread overview]
Message-ID: <20261106091922.7560-1-darwi@linutronix.de> (raw)
Hi,
A month ago in Prague I proposed a kernel configuration checker:
PREEMPT_RT configuration: Best practices with kconfig-checker
https://youtu.be/hqnOmdpGBdQ
This series adds kconfig-checker: a Python tool that checks the kernel
.config against a set of YAML rules and reports all issues by severity.
The series also adds:
- a PREEMPT_RT configuration ruleset
- a make checkconfig target
- support for ruleset overlays
Example:
$ make defconfig
$ ./tools/kconfig-checker/check.py check -c .config -r preempt_rt
Configuration Issues with severity = FATAL
==========================================
* CONFIG_PREEMPT_RT is not in .config
Rationale:
https://docs.kernel.org/core-api/real-time/kernel-configuration.html#config-preempt-rt
Configuration Issues with severity = HIGH
=========================================
* CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is unset
Rationale:
https://docs.kernel.org/core-api/real-time/kernel-configuration.html#config-cpu-freq-default-gov-performance
* Below options are set:
CONFIG_SLUB_DEBUG
Rationale:
https://docs.kernel.org/core-api/real-time/kernel-configuration.html#kernel-debug-options
Configuration Issues with severity = MEDIUM
===========================================
* Below options are set:
CONFIG_CPU_FREQ_GOV_USERSPACE
CONFIG_CPU_FREQ_GOV_ONDEMAND
Rationale:
https://docs.kernel.org/core-api/real-time/kernel-configuration.html#non-performance-cpu-frequency-governors
### ...
### More output
### ...
The same check can be run through make:
$ make RULES=preempt_rt checkconfig
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
Packages to apply additional policy or override existing mainline rules.
For example:
$ ./tools/kconfig-checker/check.py check \
-c path/to/.config \
-r preempt_rt \
-o path/to/overlay.yml
or:
$ make RULES=preempt_rt OVERLAY=path/to/overlay.yml checkconfig
Patch 09/10 documents the overlay format and gives an example use case.
My goal is to get this into the kernel and have Debian's PREEMPT_RT kernel
packaging to use it. I'd also like systemd to use it: its README lists 60
kernel CONFIG_* symbols with different requirements severity.
Thank you!
Ahmed
8<-----
Ahmed S. Darwish (10):
kconfig-checker: Add schema for rule files
kconfig-checker: Introduce PREEMPT_RT configuration rules
kconfig-checker: Add the configuration checker code
kconfig: Introduce checkconfig target
Documentation: Describe kconfig-checker usage and design
kconfig-checker: Split schema to support component reuse
kconfig-checker: Introduce overlays schema
kconfig-checker: Add support for rule overlays
Documentation: Describe kconfig-checker overlays
kconfig: Introduce OVERLAY= for make checkconfig
Documentation/admin-guide/README.rst | 29 +
.../real-time/kernel-configuration.rst | 3 +
Documentation/tools/index.rst | 1 +
Documentation/tools/kconfig_checker.rst | 101 +++
scripts/kconfig/Makefile | 25 +
tools/kconfig-checker/check.py | 686 ++++++++++++++++++
tools/kconfig-checker/rules/preempt_rt.yml | 169 +++++
tools/kconfig-checker/schemas/base.yml | 114 +++
tools/kconfig-checker/schemas/overlay.yml | 28 +
tools/kconfig-checker/schemas/rules.yml | 20 +
10 files changed, 1176 insertions(+)
create mode 100644 Documentation/tools/kconfig_checker.rst
create mode 100755 tools/kconfig-checker/check.py
create mode 100644 tools/kconfig-checker/rules/preempt_rt.yml
create mode 100644 tools/kconfig-checker/schemas/base.yml
create mode 100644 tools/kconfig-checker/schemas/overlay.yml
create mode 100644 tools/kconfig-checker/schemas/rules.yml
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
--
2.56.0
next reply other threads:[~2026-11-06 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 9:19 Ahmed S. Darwish [this message]
2026-11-06 9:19 ` [PATCH v1 01/10] kconfig-checker: Add schema for rule files Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 02/10] kconfig-checker: Introduce PREEMPT_RT configuration rules Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 03/10] kconfig-checker: Add the configuration checker code Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 04/10] kconfig: Introduce checkconfig target 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-06 9:19 ` [PATCH v1 07/10] kconfig-checker: Introduce overlays schema 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-06 9:19 ` [PATCH v1 10/10] kconfig: Introduce OVERLAY= for make checkconfig Ahmed S. Darwish
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=20261106091922.7560-1-darwi@linutronix.de \
--to=darwi@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=corbet@lwn.net \
--cc=daan.j.demeyer@gmail.com \
--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®