* Yang Zhang <yang.z.zhang@xxxxxxxxx> wrote: > diff --git a/arch/x86/kernel/irqinit.c b/arch/x86/kernel/irqinit.c > index 6e03b0d..2329a54 100644 > --- a/arch/x86/kernel/irqinit.c > +++ b/arch/x86/kernel/irqinit.c > @@ -205,6 +205,10 @@ static void __init apic_intr_init(void) > > /* IPI for X86 platform specific use */ > alloc_intr_gate(X86_PLATFORM_IPI_VECTOR, x86_platform_ipi); > +#ifdef CONFIG_HAVE_KVM > + /* IPI for KVM to deliver posted interrupt */ > + alloc_intr_gate(POSTED_INTR_VECTOR, kvm_posted_intr_ipi); > +#endif Please avoid wasting an IDT entry by reusing x86_platform_ipi. A KVM guest is in essence one type of 'x86 platform', and this callback is used by hardware platforms, so collision is not an issue AFAICS. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
