x86: irq: unconditionally define KVM interrupt vectors
authorPaolo Bonzini <pbonzini@redhat.com>
Fri, 23 Feb 2024 10:17:53 +0000 (05:17 -0500)
committerPaolo Bonzini <pbonzini@redhat.com>
Fri, 23 Feb 2024 10:23:14 +0000 (05:23 -0500)
commit0cbca1bf44a0b8666c91ce3438f235c6fe70fbf1
treeaa4c16fa8b49446122ce9b228c86b39174610774
parent687d8f4c3dea0758afd748968d91288220bbe7e3
x86: irq: unconditionally define KVM interrupt vectors

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>
arch/x86/include/asm/irq_vectors.h