Re: [PATCH v1 02/10] kconfig-checker: Introduce PREEMPT_RT configuration rules
From: Emanuele Rocca
Date: Tue Nov 17 2026 - 07:15:14 EST
Hi Ahmed,
thanks for this useful tool!
On 2026-11-06 10:19, Ahmed S. Darwish wrote:
> + - name: CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE
> + expected: y
> + severity: high
> + docs_hint: config
The docs mention the following for CPU_FREQ_DEFAULT_GOV_PERFORMANCE:
| This is not an absolute rule. Some setups might prefer to clock the
| CPU to lower speeds due to thermal packaging or other requirements. The
| key is that the CPU frequency remains constant once set.
Yet having the rule "severity: high" will presumably make
kconfig-checker require CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y in order for
validation to pass?
> + - name_pattern: CONFIG_CPU_FREQ_GOV_(CONSERVATIVE|ONDEMAND|POWERSAVE|USERSPACE)
> + expected: n
> + severity: medium
> + docs_hint: non-performance-cpu-frequency-governors
Similarly, by reading your docs, it seems to me that the worst choice
for RT workloads is ONDEMAND.
| The ONDEMAND governor should not be enabled on a real-time system. Its
| frequency changes depend on workload behavior and can significantly harm
| determinism.
Shouldn't the severity for the CPU_FREQ_GOV_ONDEMAND rule be higher,
then?