+Paolo and Stephen FYI, there's a build failure in -next due to a collision between kvm/next and tip/x86/fred. The above makes everything happy. On Thu, Feb 15, 2024, Max Kellermann wrote: > When KVM is disabled, the POSTED_INTR_* macros do not exist, and the > build fails. > > Fixes: 14619d912b65 ("x86/fred: FRED entry/exit and dispatch code") > Signed-off-by: Max Kellermann <max.kellermann@xxxxxxxxx> > --- > arch/x86/entry/entry_fred.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/arch/x86/entry/entry_fred.c b/arch/x86/entry/entry_fred.c > index ac120cbdaaf2..660b7f7f9a79 100644 > --- a/arch/x86/entry/entry_fred.c > +++ b/arch/x86/entry/entry_fred.c > @@ -114,9 +114,11 @@ static idtentry_t sysvec_table[NR_SYSTEM_VECTORS] __ro_after_init = { > > SYSVEC(IRQ_WORK_VECTOR, irq_work), > > +#if IS_ENABLED(CONFIG_KVM) > SYSVEC(POSTED_INTR_VECTOR, kvm_posted_intr_ipi), > SYSVEC(POSTED_INTR_WAKEUP_VECTOR, kvm_posted_intr_wakeup_ipi), > SYSVEC(POSTED_INTR_NESTED_VECTOR, kvm_posted_intr_nested_ipi), > +#endif > }; > > static bool fred_setup_done __initdata; > -- > 2.39.2