Messages in this thread | | | From | Thomas Gleixner <> | Subject | Re: [PATCH] x86: irq: unconditionally define KVM interrupt vectors | Date | Mon, 26 Feb 2024 16:10:05 +0100 |
| |
On Fri, Feb 23 2024 at 05:22, Paolo Bonzini wrote: > Unlike arch/x86/kernel/idt.c, FRED support chose to remove the #ifdefs > from the .c files and concentrate them in the headers, where unused > handlers are #define'd to NULL. > > However, the constants for KVM's 3 posted interrupt vectors are still > defined conditionally in irq_vectors.h. In the tree that FRED support was > developed on, this is innocuous because CONFIG_HAVE_KVM was effectively > always set. With the cleanups that recently went into the KVM tree to > remove CONFIG_HAVE_KVM, the conditional became IS_ENABLED(CONFIG_KVM). > This causes a linux-next compilation failure in FRED code, when > CONFIG_KVM=n. > > In preparation for the merging of FRED in Linux 6.9, define the interrupt > vector numbers unconditionally. > > Cc: x86@kernel.org > Reported-by: Stephen Rothwell <sfr@canb.auug.org.au> > Suggested-by: Xin Li (Intel) <xin@zytor.com> > Suggested-by: Thomas Gleixner <tglx@linutronix.de> > Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
| |