On 2012-04-24 14:59, Avi Kivity wrote: > On 04/24/2012 03:07 PM, Jan Kiszka wrote: >> On 2012-04-24 13:57, Avi Kivity wrote: >>> On 03/29/2012 09:14 PM, 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 has to manage >>>> carefully. >>>> >>>> By providing a direct injection path, we can both avoid using up limited >>>> resources and simplify the necessary steps for user land. >>>> >>>> >>> >>> Applied to queue (for 3.5). >>> >>> Thanks for your patience. >> >> Oops, that was now unexpectedly fast. > > I hope you don't mean the ~ 1 month timeframe for the whole thing. Really the last phase. I was preparing for another round of discussions. > >> Extending and slightly reformatting the API docs I noticed some >> inconsistency. Will send fixes soon. Can you fold this into my patch, or >> just apply it on top? >> >> > > Since it's just in queue, not next, will fold into parent patch. > 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
