Re: [PATCH v10 02/24] KVM: Move architecture capability Kconfigs to header defines

[Paolo Bonzini]

On 10/13/26 14:20, Steffen Eiden wrote:
> On Tue, Oct 13, 2026 at 02:13:43PM +0200, Steffen Eiden wrote:
> > 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.
> >
> > Replace global Kconfig options which only apply to one KVM
> > implementation with architecture-specific opt-in defines in the
> > respective <asm/kvm_host.h>. Only remove Kconfig symbols that would be
> > different on both s390 KVM implementations
> >
> >    - __KVM_HAVE_INVALID_WAKEUPS		(formerly HAVE_KVM_INVALID_WAKEUPS)
> >    - __KVM_HAVE_MSI			(formerly HAVE_KVM_MSI)
> >    - __KVM_HAVE_NO_POLL			(formerly HAVE_KVM_NO_POLL)
> >    - __KVM_HAVE_READONLY_MEM		(formerly HAVE_KVM_READONLY_MEM)
> >    - __KVM_HAVE_VCPU_RUN_PID_CHANGE	(formerly HAVE_KVM_VCPU_RUN_PID_CHANGE)
> >
> > This allows each architecture and guest implementation to configure its
> > supported capabilities independently in its kvm_host header and eliminates
> > adding unnecessary fallback stubs across different KVM targets.
> >
> > Acked-by: Hendrik Brueckner <brueckner@xxxxxxxxxxxxx>
> > Signed-off-by: Steffen Eiden <seiden@xxxxxxxxxxxxx>
> > ---
> >
> > Sending this patch alone. All others are OK or already picked.
> >
> > Changes for v10:
> >    - Use __KVM_HAVE_ as prefix
> >    - Clarify that this patch touches only selected Kconfig options and
> >      not all.
>
> Paolo,
>
> Sorry, I somehow managed to not CC you, doing that now.

Applied to kvm/next, thanks.

Paolo

> FWIW:
> Original patch v10:
> https://lore.kernel.org/all/20261013121343.1997112-1-seiden@xxxxxxxxxxxxx/
>
> 	Steffen