On 2012-03-29 18:46, Michael S. Tsirkin wrote: > On Thu, Mar 29, 2012 at 06:15:41PM +0200, Jan Kiszka wrote: >> Currently, MSI messages can only be injected to in-kernel irqchips by >> defining a corresponding IRQ route for each message. This is not only >> unhandy if the MSI messages are generated "on the fly" by user space, >> IRQ routes are a limited resource that user space as to manage > > > s/as/has/ Yeah, should be fixable on merge. > >> carefully. >> >> By providing a direct injection path, we can both avoid using up limited >> resources and simplify the necessary steps for user land. >> >> Signed-off-by: Jan Kiszka <jan.kiszka@xxxxxxxxxxx> > > Further, we can ensure better, deterministic worst-case performance > for real-time guests with large number of vectors. Good to hear that this is on your radar. :) > > Acked-by: Michael S. Tsirkin <mst@xxxxxxxxxx> > Thanks, Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux -- 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
