mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 02/10] kconfig-checker: Introduce PREEMPT_RT configuration rules
Date: Fri,  6 Nov 2026 10:19:14 +0100	[thread overview]
Message-ID: <20261106091922.7560-3-darwi@linutronix.de> (raw)
In-Reply-To: <20261106091922.7560-1-darwi@linutronix.de>

Introduce a kconfig-checker PREEMPT_RT rules file, matching what is at
Documentation/core-api/real-time/kernel-configuration.rst.

This will allow the tool to mechanically check the kernel's .config at a
later step.

Signed-off-by: Ahmed S. Darwish <darwi@linutronix.de>
---
 tools/kconfig-checker/rules/preempt_rt.yml | 169 +++++++++++++++++++++
 1 file changed, 169 insertions(+)
 create mode 100644 tools/kconfig-checker/rules/preempt_rt.yml

diff --git a/tools/kconfig-checker/rules/preempt_rt.yml b/tools/kconfig-checker/rules/preempt_rt.yml
new file mode 100644
index 000000000000..5c1b80adc846
--- /dev/null
+++ b/tools/kconfig-checker/rules/preempt_rt.yml
@@ -0,0 +1,169 @@
+# PREEMPT_RT .config sanitization
+#
+# SPDX-License-Identifier: GPL-2.0-only
+#
+# List all config options in alphabetic order, per group
+---
+
+docs_url: https://docs.kernel.org/core-api/real-time/kernel-configuration.html
+rules:
+  - name: CONFIG_CPU_FREQ
+    expected: y
+    severity: high
+    docs_hint: config
+
+  - name: CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE
+    expected: y
+    severity: high
+    docs_hint: config
+
+  - name_pattern: CONFIG_CPU_FREQ_GOV_(CONSERVATIVE|ONDEMAND|POWERSAVE|USERSPACE)
+    expected: n
+    severity: medium
+    docs_hint: non-performance-cpu-frequency-governors
+
+  - name: CONFIG_CPU_FREQ_GOV_SCHEDUTIL
+    expected: n
+    severity: medium
+    docs_hint: non-performance-cpu-frequency-governors
+
+  - name: CONFIG_CPU_IDLE
+    expected: y
+    severity: info
+    docs_hint: config
+
+  - name: CONFIG_DRM
+    expected: n
+    severity: info
+    docs_hint: config
+
+  - name: CONFIG_EFI_DISABLE_RUNTIME
+    expected: y
+    severity: medium
+    docs_hint: config
+
+  - name: CONFIG_NO_HZ
+    expected: n
+    severity: medium
+    docs_hint: config-no-hz-config-no-hz-full
+
+  - name: CONFIG_NO_HZ_FULL
+    expected: n
+    severity: medium
+    docs_hint: config-no-hz-config-no-hz-full
+
+  - name: CONFIG_PREEMPT_RT
+    expected: y
+    severity: fatal
+    docs_hint: config
+
+  #
+  # Tracing
+  #
+
+  - name: CONFIG_DYNAMIC_FTRACE
+    expected: y
+    severity: info
+    docs_hint: config-tracing-and-tracing-options
+
+  - name: CONFIG_FUNCTION_GRAPH_TRACER
+    expected: y
+    severity: info
+    docs_hint: config-tracing-and-tracing-options
+
+  - name: CONFIG_HWLAT_TRACER
+    expected: y
+    severity: info
+    docs_hint: config-tracing-and-tracing-options
+
+  - name: CONFIG_IRQSOFF_TRACER
+    expected: n
+    severity: high
+    docs_hint: config-irqsoff-tracer-and-config-preempt-tracer
+
+  - name: CONFIG_KPROBE_EVENTS
+    expected: y
+    severity: info
+    docs_hint: config-tracing-and-tracing-options
+
+  - name: CONFIG_PREEMPT_TRACER
+    expected: n
+    severity: high
+    docs_hint: config-irqsoff-tracer-and-config-preempt-tracer
+
+  - name: CONFIG_SCHED_TRACER
+    expected: y
+    severity: info
+    docs_hint: config-tracing-and-tracing-options
+
+  - name: CONFIG_TRACING
+    expected: y
+    severity: info
+    docs_hint: config-tracing-and-tracing-options
+
+  - name: CONFIG_UPROBE_EVENTS
+    expected: y
+    severity: info
+    docs_hint: config-tracing-and-tracing-options
+
+  #
+  # Debugging
+  #
+
+  - name_pattern: CONFIG_DEBUG_.*
+    expected: n
+    severity: medium
+    docs_hint: kernel-debug-options
+
+  - name: CONFIG_DEBUG_ATOMIC_SLEEP
+    expected: allowed
+    severity: low
+
+  - name: CONFIG_DEBUG_BOOT_PARAMS
+    expected: allowed
+    severity: low
+
+  - name: CONFIG_DEBUG_BUGVERBOSE
+    expected: allowed
+    severity: low
+
+  - name: CONFIG_DEBUG_FS
+    expected: allowed
+    severity: low
+
+  - name: CONFIG_DEBUG_FS_ALLOW_ALL
+    expected: allowed
+    severity: low
+
+  - name: CONFIG_DEBUG_INFO
+    expected: allowed
+    severity: low
+
+  - name: CONFIG_DEBUG_INFO_NONE
+    expected: allowed
+    severity: low
+
+  - name: CONFIG_DEBUG_KERNEL
+    expected: allowed
+    severity: low
+
+  - name: CONFIG_DEBUG_MISC
+    expected: allowed
+    severity: low
+    rationale:
+      A menu option which enables the display of other debug symbols.
+
+  - name: CONFIG_LOCKUP_DETECTOR
+    expected: n
+    severity: high
+    docs_hint: config
+
+  - name: CONFIG_PROVE_LOCKING
+    expected: n
+    severity: high
+    docs_hint: config
+
+  - name_pattern: CONFIG_SLUB_DEBUG.*
+    expected: n
+    severity: high
+    docs_hint: kernel-debug-options
-- 
2.56.0


  parent 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 [PATCH v1 00/10] tools: Introduce a kernel configuration checker Ahmed S. Darwish
2026-11-06  9:19 ` [PATCH v1 01/10] kconfig-checker: Add schema for rule files Ahmed S. Darwish
2026-11-06  9:19 ` Ahmed S. Darwish [this message]
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-3-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®