Re: [PATCH v8 08/29] KVM: Move architecture capability Kconfigs to header defines

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] kconfig: syntax error in virt/kvm/Kconfig due to 'booCONFIG_ltt' typo
--

commit ee51b43b92593e9aef02197487e12632baf77f58
Author: Steffen Eiden <seiden@linux.ibm.com>

KVM: Move architecture capability Kconfigs to header defines

Historically, KVM feature opt-ins and callbacks (e.g. read-only memory,
MSI routing, generic pre-fault memory, lockless aging, halt-polling
controls, and vcpu run PID changes) were configured globally via Kconfig
symbols (CONFIG_HAVE_KVM_* and CONFIG_KVM_*).

With s390 hosting multiple independent KVM implementations within the
same kernel build (native s390 KVM and arm64 on s390), global Kconfig
selections force both implementations to inherit options that only apply
to one of them.

> diff --git a/virt/kvm/Kconfig b/virt/kvm/Kconfig
> index c3c0ee253fc77..008b110ebdb7a 100644
> --- a/virt/kvm/Kconfig
> +++ b/virt/kvm/Kconfig
> @@ -9,7 +9,7 @@ config KVM_COMMON
>         select PREEMPT_NOTIFIERS
>  
>  config HAVE_KVM_PFNCACHE
> -       bool
> +       booCONFIG_ltt

[Severity: Low]
Is booCONFIG_ltt a typo for bool under config HAVE_KVM_PFNCACHE in
virt/kvm/Kconfig?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260918133107.1042730-1-seiden@linux.ibm.com?part=8