Hello! > KVM GSI routing, even if only used for MSI routing then mandates to > build entries for non MSI IRQs, using irqchip routing entries. Then you > draw the irqchip.c kvm_irq_routing_table > chip[KVM_NR_IRQCHIPS][KVM_IRQCHIP_NUM_PINS] static allocation issue. Sorry for this add-on, needed time to look at the code. Actually, if we don't use this code at all, and implement our own kvm_set_irq_routing() and kvm_free_irq_routing(), we don't have to bother about all these limitations. The simplest thing to do there would be to store GSI number in struct its_itte. In this case raising an MSI by GSI would not differ from what i currently do. Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia -- 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
