Re: [PATCH 2/4] xen: Drop CONFIG_XEN_PVHVM
Andrew Cooper <[email protected]>
| Newsgroups | org.xenproject.lists.xen-devel,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 05/08/2026 9:21 am, Juergen Gross wrote: > On x86 CONFIG_XEN_PVHVM is now a synonym of CONFIG_XEN. > > In Xen specific x86 code it can be just dropped, in non-Xen specific > x86 code it can be replaced with CONFIG_XEN. > > In architecture independent code it is used only where CONFIG_XEN is > defined, so it can be replaced with CONFIG_X86 there. > > Signed-off-by: Juergen Gross <[email protected]> > > diff --git a/arch/x86/include/asm/idtentry.h b/arch/x86/include/asm/idtentry.h > index 20f548702404..f400cfac69a6 100644 > --- a/arch/x86/include/asm/idtentry.h > +++ b/arch/x86/include/asm/idtentry.h > @@ -745,7 +745,7 @@ DECLARE_IDTENTRY_SYSVEC(HYPERV_STIMER0_VECTOR, sysvec_hyperv_stimer0); > DECLARE_IDTENTRY_SYSVEC(HYPERVISOR_CALLBACK_VECTOR, sysvec_acrn_hv_callback); > #endif > > -#ifdef CONFIG_XEN_PVHVM > +#ifdef CONFIG_XEN > DECLARE_IDTENTRY_SYSVEC(HYPERVISOR_CALLBACK_VECTOR, sysvec_xen_hvm_callback); > #endif I'm very happy to see a reduction in the number of Kconfig symbols for Xen (there are definitely too many), but this looks wonky. Or are you saying that there really is no way to build a Xen PV guest excluding the HVM-only bits? ~Andrew